kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #40698 from kardashov/patch-1 

Fix spelling error in “Migrate from PodSecurityPolicy to the Built-In PodSecurity Admission Controller”
This commit is contained in:
Kubernetes Prow Robot 2023-04-17 01:38:42 -07:00 committed by GitHub
parent 9cdcb2c77c 5ed63def8a
commit 00104ae650
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/tasks/configure-pod-container/migrate-from-psp.md
View File

@ -201,7 +201,7 @@ For each updated PodSecurityPolicy:
3. Create the new PodSecurityPolicies. If any Roles or ClusterRoles are granting `use` on all PSPs 3. Create the new PodSecurityPolicies. If any Roles or ClusterRoles are granting `use` on all PSPs
this could cause the new PSPs to be used instead of their mutating counter-parts. this could cause the new PSPs to be used instead of their mutating counter-parts.
4. Update your authorization to grant access to the new PSPs. In RBAC this means updating any Roles 4. Update your authorization to grant access to the new PSPs. In RBAC this means updating any Roles
or ClusterRoles that grant the `use` permision on the original PSP to also grant it to the or ClusterRoles that grant the `use` permission on the original PSP to also grant it to the
updated PSP. updated PSP.
5. Verify: after some soak time, rerun the command from step 1 to see if any pods are still using 5. Verify: after some soak time, rerun the command from step 1 to see if any pods are still using
the original PSPs. Note that pods need to be recreated after the new policies have been rolled the original PSPs. Note that pods need to be recreated after the new policies have been rolled