-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Pod Security Admission docs for graduation to stable #35618
Conversation
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
/lgtm |
LGTM label has been added. Git tree hash: 2ac4db2f536f7c1f9e7a67c9001ad0ff5384eae3
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: this page sets min-kubernetes-server-version: v1.22
in the front matter, but actually we can omit that line (and it's now possibly a bit misleading).
/sig auth |
/milestone 1.25 |
Kubernetes offers a built-in _Pod Security_ {{< glossary_tooltip text="admission controller" | ||
term_id="admission-controller" >}} to enforce the Pod Security Standards. Pod security restrictions | ||
are applied at the {{< glossary_tooltip text="namespace" term_id="namespace" >}} level when pods are | ||
created. | ||
|
||
## {{% heading "prerequisites" %}} | ||
|
||
To use this mechanism, your cluster must enforce Pod Security admission. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unrelated and complete nit, but why is this a prerequisite? To use this feature, your cluster must...use this feature? Feels like you could get rid of the heading altogether and convert the heading after it from an H3 to an H2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We usually save
## {{% heading "prerequisites" %}}
for task or tutorial pages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, when features graduate to stable, we do expect to polish the docs and fix nits like this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have a standard format for saying a built-in admission controller must be enabled (or really, must not be disabled)? Looking at a few other admission-related pages, it seems like most of them just omit the prerequisites.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just deleted it for now.
/label tide/merge-method-squash |
/remove-label tide/merge-method-squash 2 commits are fine. |
Changes since #35618 (comment) are not material. /lgtm |
/approve |
LGTM label has been added. Git tree hash: ae4aaadf7f15ddce5ea64bae76c7e5b17f5d73a7
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Update the PSA docs for stable release in v1.25
Includes:
/assign @liggitt