Question

You are troubleshooting a Deployment named 'web' and run 'kubectl edit deployment web' to change the container image directly. The change takes effect and Pods roll out with the new image. However, your teammate points out that these edits are not tracked in the Git repository where all manifests are stored. What is the most accurate description of what you did and its consequence?

Accepted Answer

You modified the live object in the cluster directly; the change is applied but now diverges from the source manifest, so a future 'kubectl apply' of the Git manifest can overwrite it.

Answer

You edited a local file only; the cluster state is unchanged until you run 'kubectl apply -f' against the same file.

Answer

The edit is permanent and cannot be overwritten because 'kubectl edit' writes to etcd with higher priority than 'kubectl apply'.

Answer

The edit only affected the ReplicaSet, so the Deployment spec in the cluster still shows the old image.