From 7ae915bb0c88095acfc9e4a66c997fbc8cfedd02 Mon Sep 17 00:00:00 2001 From: Slava Semushin Date: Wed, 13 Dec 2017 17:25:45 +0100 Subject: [PATCH] concepts/policy/pod-security-policy.md: fix broken links. --- docs/concepts/policy/pod-security-policy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/concepts/policy/pod-security-policy.md b/docs/concepts/policy/pod-security-policy.md index f1373a7130..ad9a75e257 100644 --- a/docs/concepts/policy/pod-security-policy.md +++ b/docs/concepts/policy/pod-security-policy.md @@ -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 -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 [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 would be able to create privileged containers. For more details on configuring Controller Manager authorization, see [Controller -Roles](docs/admin/authorization/rbac/#controller-roles). +Roles](/docs/admin/authorization/rbac/#controller-roles). ## Policy Order