Skip to content

Commit ba857cc

Browse files
committed
Update content/en/docs/setup/best-practices/enforcing-pod-security-standards.md
1 parent c367021 commit ba857cc

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/en/docs/setup/best-practices/enforcing-pod-security-standards.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ namespace, and by referencing the Pod Security Standards, decide on an appropria
2828
each of them. Unlabeled namespaces should only indicate that they've yet to be evaluated.
2929

3030
In the scenario that all workloads in all namespaces have the same security requirements,
31-
we provide an [example](/docs/concepts/security/pod-security-admission/#applying-to-all-namespaces)
31+
we provide an [example](/docs/tasks/configure-pod-container/enforce-standards-namespace-labels/#applying-to-all-namespaces)
3232
that illustrates how the PodSecurity labels can be applied in bulk.
3333

3434
### Embrace the principle of least privilege

0 commit comments

Comments
 (0)