Open AnshumanTripathi opened 1 month ago
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.
/sig security
Out of all the sections we have, the concepts section feels like the least bad home.
@sftim what are your thoughts about moving them to docs/setup/best-practices
https://kubernetes.io/docs/setup/best-practices/ ?
@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.
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
Ah, I was wrong! Maybe that is OK then.
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.
Regarding this comment https://github.com/kubernetes/website/pull/45080#discussion_r1751203955, 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?