Kubernetes / Deployments, Scheduling & Batch Workloads
Review Deployment history before choosing a rollback target
A rollback needs the correct application revision and compatible external state. Inspect retained controller history first.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl -n app rollout history deployment/webRead the result
The history shows retained revisions, subject to revision limits and annotations. It does not back up ConfigMaps, Secrets, persistent data or database migrations.
Resolve and verify
Compare the candidate revision with the approved release and external dependencies. Plan a reviewed rollback and verify business behavior afterward.
Before changing production
Do not assume reverting a Pod template reverses every effect of a deployment.