diff options
| author | Mike Danese <mikedanese@gmail.com> | 2015-08-05 18:08:26 -0700 |
|---|---|---|
| committer | Mike Danese <mikedanese@gmail.com> | 2015-08-05 21:11:11 -0700 |
| commit | a74ffb6a381cf9a7bd8282c8d9806bae41680f3d (patch) | |
| tree | 084fc6560a7f3dd69b1e4dd08122a9338468e296 /security_context.md | |
| parent | a38fc0660419c1d5c2b460a459d8b93f996f79c8 (diff) | |
rewrite all links to issues to k8s links
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 7a80c01d..4704caab 100644 --- a/security_context.md +++ b/security_context.md @@ -42,7 +42,7 @@ A security context is a set of constraints that are applied to a container in or ## Background -The problem of securing containers in Kubernetes has come up [before](https://github.com/GoogleCloudPlatform/kubernetes/issues/398) and the potential problems with container security are [well known](http://opensource.com/business/14/7/docker-security-selinux). Although it is not possible to completely isolate Docker containers from their hosts, new features like [user namespaces](https://github.com/docker/libcontainer/pull/304) make it possible to greatly reduce the attack surface. +The problem of securing containers in Kubernetes has come up [before](http://issue.k8s.io/398) and the potential problems with container security are [well known](http://opensource.com/business/14/7/docker-security-selinux). Although it is not possible to completely isolate Docker containers from their hosts, new features like [user namespaces](https://github.com/docker/libcontainer/pull/304) make it possible to greatly reduce the attack surface. ## Motivation |