add entry for naked pod

[dejanu]

Add a new entry for naked-pod to Glossary

Closes issue #51235

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign nate-double-u for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• content/en/docs/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	1e04a67
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/6849ac2580f01700084dcc05
😎 Deploy Preview	https://deploy-preview-51236--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[lmktfy]

Thanks for the suggestion.

Could we call these a bare Pod? Naked is harder to localize and can have connotations we don't want.

[shurup]

Based on quick grep: while the "naked pod" term is used twice in the only document (concepts/configuration/overview.md), "bare pods" are mentioned on several pages (all belong to the concepts/workloads/controllers/ directory and once in a task). I guess we'll need to make it consistent throughout all documentation pages.

[reylejano]

Suggested change

	Naked Pods will not be rescheduled in the event of a node failure.
	Naked Pods will not be rescheduled in the event of a node failure.

Is this true if the pod's .spec.restartPolicy is set to Always

[reylejano]

+1 to @lmktfy and @shurup 's comment to use bare pods

[tengqm]

I'm leaning towards not adding this glossary.
If we need some clarification of "naked pod" or "bare pod", it means we should avoid using these terms.
Neither "naked pod" nor "bare pod" is widely used elsewhere AFAICT.
When we refer to something as A,

• if A is widely used across the community but it could be new to beginners, we can add a glossary for it;
• if A is used only as a metaphor and that metaphor may cause confusion, we should consider remove that metaphor rather than adding more texts to explain it.

In summary, please stop making a complex thing more complex!

[lmktfy]

The "bare Pod" concept is used only a few times on the web. I saw three.

Rewriting our existing pages, and adding no terminology for it, looks viable. We could call it a "Pod with no owners", for example.

[dejanu]

I'm leaning towards not adding this glossary. If we need some clarification of "naked pod" or "bare pod", it means we should avoid using these terms. Neither "naked pod" nor "bare pod" is widely used elsewhere AFAICT. When we refer to something as A,

• if A is widely used across the community but it could be new to beginners, we can add a glossary for it;
• if A is used only as a metaphor and that metaphor may cause confusion, we should consider remove that metaphor rather than adding more texts to explain it.

In summary, please stop making a complex thing more complex!

@tengqm completely agreeing with you there's no need for bikeshedding, my perspective on the matter is that it can be added since personally I've seen beginners asking about naked Pod naming (in the context of static Pods) and at a quick glance, I could find some references to naked pod:

https://kubernetes.io/docs/concepts/configuration/overview/#naked-pods-vs-replicasets-deployments-and-jobs

https://learn.microsoft.com/en-us/azure/aks/policy-reference

https://hub.armosec.io/docs/c-0073