Kubernetes / Deployments, Scheduling & Batch Workloads
Check StatefulSet update policy when replicas remain on different revisions
Some StatefulSets intentionally retain older Pods because of partitioned or OnDelete updates. Inspect policy before forcing replacement.
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 get statefulset database -o jsonpath='{.spec.updateStrategy}{" "}{.status.currentRevision}{" "}{.status.updateRevision}'Read the result
The strategy and revision identifiers explain intended controller behavior. They do not prove the application can safely mix versions.
Resolve and verify
Compare the configured policy and Pod revisions with the staged release plan. Advance only the approved step and validate application replication and health.
Before changing production
Do not replace every replica at once or assume stateless Deployment rollback rules apply to persistent clustered data.