Pod Restructuring: Create Advanced Pod Configuration page

[Caesarsage]

This is a Feature Request

What would you like to be added
Restructuring https://kubernetes.io/docs/concepts/workloads/pods/
Move advanced configuration content from Pod page to dedicated advanced page:

• Move Priority classes, runtime classes content to /docs/concepts/workloads/pods/advanced-pod-config/
• Move detailed security context configuration to advanced page
• Move node selection details (affinity, tolerations) to advanced page
• Replace with brief mentions and links to advanced page
• Keep only basic Pod specification examples on main page

Why is this needed
These advanced topics currently scattered in main Pod page make it overwhelming for beginners. A dedicated page serves platform engineers and advanced users better.

Comment
Related to issue #38867 Pod documentation restructure. Creates destination for advanced content before removing it from main page.

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

[lmktfy]

I suggest that Pod OS isn't moved to the advanced configuration page. I mostly agree with the other changes.

In some clusters (ie: anything with multiple node families), setting the Pod OS is a strongly recommended good practice. It's niche but sometimes it's really important to get right.

[Caesarsage]

I suggest that Pod OS isn't moved to the advanced configuration page. I mostly agree with the other changes.

In some clusters (ie: anything with multiple node families), setting the Pod OS is a strongly recommended good practice. It's niche but sometimes it's really important to get right.

okay, i agree

[Caesarsage]

/assign

[Caesarsage]

/language en

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten