approval gates for agent-initiated deploys

TL;DR

An agent should prepare a deploy all the way to the doorstep and then wait for a human tap. Implement that with native gates: paused rollouts, environment protection rules, or a chatops approve command. The agent proposes the exact diff and the exact command; the human approves the diff, and the system runs the command.

Error / query

approval gates for agent-initiated deploys

Use this skill when

• an agent builds or prepares production deploys
• you need a human in the loop before anything ships
• a deploy pipeline is being extended to accept agent input
• auditors ask who authorized each production release

Not for this skill when

• deploys are fully automated with no agent involved (existing CD approvals already cover it)
• the target is dev or staging
• you want the agent to approve its own changes (that is not a gate)

Steps

Step 1: Define what needs a gate and what does not

grep -r "auto-promote\|require-approval" /opt/gitops/policies/ | head -10

Expected: a written policy listing which change classes need approval (prod deploys, stateful restarts, config changes) and which do not (dev deploys, read-only). If everything needs a tap, humans rubber-stamp; if nothing does, the gate is theater.

Step 2: Use a paused rollout as the Kubernetes-native gate

kubectl argo rollouts get rollout [APP] -n prod -o jsonpath="{.status.pauseConditions}"
kubectl argo rollouts promote [APP] -n prod

Expected: the first command shows the rollout paused awaiting promotion; the second (run by the human, not the agent) resumes it. The agent prepares the rollout and stops; promotion is a separate human action with its own audit entry.

Step 3: Protect the deploy environment in your Git host

gh api repos/[ORG]/[REPO]/environments/prod --jq ".protection_rules[].type"

Expected: protection rule types like required_reviewers listed. The agent can open the PR and pass CI, but the environment blocks the deploy job until a required reviewer approves; the agent cannot approve its own run.

Step 4: Give the human a one-command approve path

kubectl annotate rollout [APP] -n prod ops.example.com/approved-by="[HUMAN]" ops.example.com/approved-at="[TIMESTAMP]"

Expected: the approval recorded as annotations on the rollout object. Chatops ("approve deploy 1234") should land here too: the approval must be a durable, attributed record, not a Slack message that scrolls away.

Step 5: Verify the gate cannot be bypassed by the agent

kubectl auth can-i promote rollouts --as=system:serviceaccount:ops:sre-agent -n prod

Expected: "no". The agent's RBAC must lack the promote/approve verbs, and the environment rules must not count the agent as a reviewer. Test the bypass path in staging: ask the agent to ship without approval and confirm every layer refuses.

Variant phrasing

"human in the loop for ai deploys"

Same mechanism. The human reviews the diff the agent prepared, taps approve once, and the system executes; the agent never holds the approve capability itself.

"agent opened a deploy PR, now what"

CI runs, the agent's diff gets reviewed like any other PR, required reviewers approve, and the protected environment lets the deploy job proceed.

"emergency deploy without approval"

Keep a documented break-glass path with its own alerting and mandatory post-hoc review; the gate handles the 99 percent case, break-glass handles the pager at 3am, and both leave audit trails.

Why it happens

Agents are fast and confident, which is exactly the wrong combination for unsupervised deploys: a wrong-but-plausible change ships in seconds with no hesitation. The gate reintroduces the hesitation at the right place, after all the preparation work is done, so the human decision is cheap (review a diff, tap once) instead of expensive (do the whole deploy manually). Approval gates do not slow agents down much; they catch the fraction of changes where speed would have been a mistake.

Edge cases and pitfalls

• Rubber-stamping kills the gate's value; keep the approval scope tight so each tap gets real attention.
• Time-box approvals: a gate that waits forever blocks rollbacks too, so auto-expire stale approvals and require re-review.
• The agent preparing the deploy must not be able to edit the gate policy; separate who writes manifests from who writes policy.
• Multi-step deploys need the gate at the prod boundary specifically, not on every intermediate step, or teams route around it.
• Record what was approved (the exact diff hash), not just that something was approved; otherwise the agent can swap the payload after the tap.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_HMRbDb5lZKivm9KjZFN-wg