Re: [kubernetes/kubernetes] kubectl allows editing/patching static manifest pods though changes are not applied (mostly) (#63035)

[k8s-ci-robot]

@losipiuk: Reiterating the mentions to trigger a notification:
@kubernetes/sig-cli-bugs

In response to this:

cc @kubernetes/sig-cli-bugs (not sure if this is right group though).

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[Jordan Liggitt]

It is neither an error nor a bug. The API manifestations of static pods behave as any other API object (the apiserver doesn't generally treat them specially). The difference is that the kubelet treats the manifests as the authoritative source, not the API.

On a subsequent reconciliation loop, the kubelet will likely overwrite the changes made to the pod.

[Jordan Liggitt]

/close

[k8s-ci-robot]

Closed #63035.

[Gayatri S Ajith]

In case someone has the same question and reaches this page
When you execute kubectl edit/path for a static object only the spec of the mirror object changes. The actual static pod is not affected. If you execute docker ps and check the actual container you will notice that nothing has changed.

Of course, the discrepancy is confusing but, at least the integrity of the static pod is maintained.

—
You are receiving this because you are on a team that was mentioned.

Reply to this email directly, view it on GitHub, or unsubscribe.