diff options
| author | Paul Morie <pmorie@redhat.com> | 2015-05-06 10:04:39 -0400 |
|---|---|---|
| committer | Paul Morie <pmorie@redhat.com> | 2015-05-06 10:04:39 -0400 |
| commit | 24906a08ebbce50f3a4db4b3052f102bffa5bbe7 (patch) | |
| tree | cb496d3a64a8713845f33ecf5681914d5384ae76 /security_context.md | |
| parent | ff2913cfb3328510a869c29f5ee950d6c650a43f (diff) | |
Fix link to service accounts doc in security context doc
Diffstat (limited to 'security_context.md')
| -rw-r--r-- | security_context.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/security_context.md b/security_context.md index cd10202e..62e203a5 100644 --- a/security_context.md +++ b/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 |