hard20 pts · first answer countsgitopskubernetesincident-response

Hotfix keeps disappearing

During an incident an engineer runs kubectl set image to deploy a hotfix. A minute later the old image is back. The cluster is managed by Argo CD with automated sync and self-heal. What is the right response?

A.Restart the Argo CD controller so it forgets the old image.B.Self-heal is reverting the manual drift to match Git; commit the hotfix image to the Git repo (or pause auto-sync for that app with a documented reason) so Git stays the source of truth.C.Delete the Deployment and recreate it with kubectl apply.D.Self-heal only applies to ConfigMaps, so this must be a Kubernetes bug.

← Rolling update that never finishes Renaming a column with zero downtime →