Senior Site Reliability Engineer (SRE), Kubernetes specialist & Multi cloud Architect.
Colecionador de perfumes, capitais do mundo e certificações profissionais.
Great article on the operational tidbits of static pods.
I'd just give an emphasys on the fact that, to make a way for people to actually know that static pods exists, Kubelet communicates to their Apiserver the fact, so it shows when you give kubectl commands.
The important part is to comprehend that it is purely informational - as the documentation mentions, iirc, it is a "mirror image of the Pod".
As such, if you try kubectl delete on them, you're instructing APIServer to remove the mirror image, and it most definitely won't restart the real static pod.
It might not feel all that relevant, but if you deploy something that is referenced by the manifest (like certificates ou service account signing keys) it won't reload just because you deleted the mirror image, you'd have to restart/reload it on the node.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great article on the operational tidbits of static pods.
I'd just give an emphasys on the fact that, to make a way for people to actually know that static pods exists, Kubelet communicates to their Apiserver the fact, so it shows when you give kubectl commands.
The important part is to comprehend that it is purely informational - as the documentation mentions, iirc, it is a "mirror image of the Pod".
As such, if you try kubectl delete on them, you're instructing APIServer to remove the mirror image, and it most definitely won't restart the real static pod.
It might not feel all that relevant, but if you deploy something that is referenced by the manifest (like certificates ou service account signing keys) it won't reload just because you deleted the mirror image, you'd have to restart/reload it on the node.