Move Hardening guides out of concepts section

[AnshumanTripathi]

Regarding this comment #45080 (comment), we should consider moving security hardening guides out of concepts. It cannot be moved to references either. Should we move it to a new section?

[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.

Details

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.

[AnshumanTripathi]

/sig security

[sftim]

Out of all the sections we have, the concepts section feels like the least bad home.

• it's explaining what you might need to consider to secure your cluster
• it is not task documentation where following it unquestioningly produces a specific outcome
• it is not really a tutorial or a setup guide
• it is not reference documentation

[AnshumanTripathi]

@sftim what are your thoughts about moving them to docs/setup/best-practices https://kubernetes.io/docs/setup/best-practices/ ?

[sftim]

@sftim what are your thoughts about moving them to docs/setup/best-practices https://kubernetes.io/docs/setup/best-practices/ ?

We shouldn't move them to a section about good practice for large clusters. Even small clusters may need to have strong information security.

[AnshumanTripathi]

That section is not specific for large clusters 🤔 . For example since we already have Enforcing pod security standards, maybe the hardening guides could also be alongside this doc

[sftim]

Ah, I was wrong! Maybe that is OK then.

[network-charles]

The content of the page fits into the best practices folder.

content/en/docs/setup/best-practices

For example, all sub-sections in the section "kube-scheduler configuration" describe some best practices while using those command line options.

[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

[AmarNathChary]

/remove-lifecycle stale