concepts/policy/pod-security-policy.md: fix broken links.
This commit is contained in:
@@ -127,7 +127,7 @@ paired with system groups to grant access to all pods run in the namespace:
|
|||||||
```
|
```
|
||||||
|
|
||||||
For more examples of RBAC bindings, see [Role Binding
|
For more examples of RBAC bindings, see [Role Binding
|
||||||
Examples](docs/admin/authorization/rbac/#role-binding-examples). For a complete
|
Examples](/docs/admin/authorization/rbac/#role-binding-examples). For a complete
|
||||||
example of authorizing a PodSecurityPolicy, see
|
example of authorizing a PodSecurityPolicy, see
|
||||||
[below](#example).
|
[below](#example).
|
||||||
|
|
||||||
@@ -140,7 +140,7 @@ have superuser permissions. Otherwise requests would bypass authentication and
|
|||||||
authorization modules, all PodSecurityPolicy objects would be allowed, and users
|
authorization modules, all PodSecurityPolicy objects would be allowed, and users
|
||||||
would be able to create privileged containers. For more details on configuring
|
would be able to create privileged containers. For more details on configuring
|
||||||
Controller Manager authorization, see [Controller
|
Controller Manager authorization, see [Controller
|
||||||
Roles](docs/admin/authorization/rbac/#controller-roles).
|
Roles](/docs/admin/authorization/rbac/#controller-roles).
|
||||||
|
|
||||||
## Policy Order
|
## Policy Order
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user