Update content/en/docs/setup/best-practices/enforcing-pod-security-standards.md
This commit is contained in:
parent
c367021bf0
commit
ba857ccda1
|
|
@ -28,7 +28,7 @@ namespace, and by referencing the Pod Security Standards, decide on an appropria
|
|||
each of them. Unlabeled namespaces should only indicate that they've yet to be evaluated.
|
||||
|
||||
In the scenario that all workloads in all namespaces have the same security requirements,
|
||||
we provide an [example](/docs/concepts/security/pod-security-admission/#applying-to-all-namespaces)
|
||||
we provide an [example](/docs/tasks/configure-pod-container/enforce-standards-namespace-labels/#applying-to-all-namespaces)
|
||||
that illustrates how the PodSecurity labels can be applied in bulk.
|
||||
|
||||
### Embrace the principle of least privilege
|
||||
|
|
|
|||
Loading…
Reference in New Issue