Question

Your team manages a production cluster with Argo CD following GitOps principles. The Git repository is the single source of truth for the Deployment manifests. During an incident, an engineer runs 'kubectl scale deployment web --replicas=10' directly against the cluster to handle a traffic spike, but does not update the Git repository. Argo CD is configured with automated sync and self-heal enabled. What will happen to the manual change?

Accepted Answer

Argo CD detects the drift from the Git-declared state and reverts the Deployment back to the replica count defined in the repository.

Answer

Argo CD permanently accepts the live change and updates the Git repository to match the new replica count.

Answer

Argo CD marks the application as Healthy and leaves the manual change in place until the next Git commit.

Answer

Argo CD deletes the Deployment entirely because the live state no longer matches the manifest.