From a6b06f49320daa257e1707ab4a8b2bdac2cae985 Mon Sep 17 00:00:00 2001 From: Paul Morie Date: Wed, 6 May 2015 10:04:39 -0400 Subject: [PATCH] Fix link to service accounts doc in security context doc --- docs/design/security_context.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/design/security_context.md b/docs/design/security_context.md index cd10202e5fc..62e203a5549 100644 --- a/docs/design/security_context.md +++ b/docs/design/security_context.md @@ -32,7 +32,7 @@ Processes in pods will need to have consistent UID/GID/SELinux category labels i * The concept of a security context should not be tied to a particular security mechanism or platform (ie. SELinux, AppArmor) * Applying a different security context to a scope (namespace or pod) requires a solution such as the one proposed for - [service accounts](https://github.com/GoogleCloudPlatform/kubernetes/pull/2297). + [service accounts](./service_accounts.md). ## Use Cases