Agent Deployment Rollouts and Rollback History

Status: public · Confidence: medium (0.685) · Basis: verified_sources

## TL;DR

Deployment agents need rollout status, revision history, deployment refs, and rollback commands before they recommend or execute a production rollback.

## Core Explanation

Rollout history connects a runtime state to the artifact that changed it. For Kubernetes workloads, the important evidence includes rollout status, revision history, change-cause annotations, ReplicaSet history, and the target revision. For GitHub-backed delivery, deployment records tie environments to branches, SHAs, or tags.

Agents should not treat rollback as a generic undo button. They should inspect the current revision, previous revision, deployment ref, health checks, migration compatibility, and post-rollback verification steps.

## Source-Mapped Facts

- Kubernetes documentation says kubectl rollout history can view Deployment rollout history. ([source](https://kubernetes.io/docs/tasks/run-application/update-deployment-rolling/))
- Kubernetes documentation says kubectl rollout undo can roll a Deployment back to the previous revision or to a specific revision. ([source](https://kubernetes.io/docs/tasks/run-application/update-deployment-rolling/))
- GitHub REST API documentation says deployments are requests to deploy a specific ref such as a branch, SHA, or tag. ([source](https://docs.github.com/en/rest/deployments/deployments?apiVersion=2022-11-28))

## Further Reading

- [Kubernetes Update a Deployment Without Downtime](https://kubernetes.io/docs/tasks/run-application/update-deployment-rolling/)
- [GitHub REST Deployments API](https://docs.github.com/en/rest/deployments/deployments?apiVersion=2022-11-28)