From d4d64ea35ea237a040e26a105b893b037b355fd9 Mon Sep 17 00:00:00 2001 From: Peter Lee Date: Thu, 13 Apr 2017 19:19:50 +0800 Subject: [PATCH] fix link --- docs/concepts/policy/security-context.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/policy/security-context.md b/docs/concepts/policy/security-context.md index 7b7449e22f..f8e921f44c 100644 --- a/docs/concepts/policy/security-context.md +++ b/docs/concepts/policy/security-context.md @@ -6,7 +6,7 @@ assignees: title: Security Context --- -A security context defines the operating system security settings (uid, gid, capabilities, SELinux role, etc..) applied to a container. See [security context design](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/security_context.md) for more details. +A security context defines the operating system security settings (uid, gid, capabilities, SELinux role, etc..) applied to a container. See [security context design](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/security-context-constraints.md) for more details. There are two levels of security context: pod level security context, and container level security context.