Unable to edit a Pod : “Edit cancelled, no valid changes were saved” — K8s

In Kubernetes, flexibility and configuration management are crucial for maintaining robust containerized applications. However, you may encounter challenges when trying to edit the specifications of an existing pod. One common error is the inability to modify certain aspects of a pod, often leading to messages like “Pods [pod-name] is invalid” with no valid changes saved. This issue arises due to the immutable nature of some pod specifications.

FULL ARTICLE :

https://sarankamandula.medium.com/unable-to-edit-a-pod-it-throws-an-error-edit-cancelled-no-valid-changes-were-saved-k8s-90f02f671c8f

Why Can’t You Edit Your Pod?

Kubernetes pods, once created, have certain fields that are immutable. This means you cannot change these fields directly if the pod is already running. Common scenarios where this limitation becomes apparent include attempts to modify container specifications or other critical parameters. In this blog post, we’ll explore why these restrictions exist, what you can and cannot change, and how to work around these limitations effectively.

Edit a POD

Remember, you CANNOT edit specifications of an existing POD other than the below.

• spec.containers[*].image
• spec.initContainers[*].image
• spec.activeDeadlineSeconds
• spec.tolerations

By understanding these limitations, you’ll be better equipped to make the necessary adjustments to your deployments or configurations.

1. First, we need to edit the pod that is currently created.

kubectl edit pod <pod_name>        

2. This command is used to edit a pod. When you made certain changes, and try to save the file, it denies (see the screenshot below). This is because you are attempting to edit a field on the pod that is not editable.

3. When you override it, a copy of the file with your changes is saved in a temporary location as shown below.

Path: /tmp/kubectl-edit-2887539248.yaml        

4. Now, the recommended option is to delete the existing pod by running the below command.

Kubectl delete pod <pod_name>        

5. Then create a new pod with your changes using the temporary file

Kubectl create -f /tmp/kubectl-edit-2887539248.yaml        

This command restores the deleted pod but with the updated configuration.

There are many common errors that we see on a day-day basis in K8s. I’d like to highlight this error which commonly occurs while editing a file, so be mindful with the steps, solution provided and create your manifest files.

READ THE FULL ARTICLE HERE:

https://sarankamandula.medium.com/unable-to-edit-a-pod-it-throws-an-error-edit-cancelled-no-valid-changes-were-saved-k8s-90f02f671c8f