whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update security-context.md (#7366)

Browse Source 
* Update security-context.md

The old link to `PodSecurityContext` was 404. Found another one by starting from a `Pod` in the API Reference. Hope it is the appropriate one.

* Fix broken link to SecurityContext
This commit is contained in:
Martin Mosegaard Amdisen
2018-02-12 23:05:50 +01:00
committed by k8s-ci-robot
parent 8c3094c26f
commit 89f0769650
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tasks/configure-pod-container/security-context.md
+2 -2
View File
@@ -43,7 +43,7 @@ For more information about security mechanisms in Linux, see
To specify security settings for a Pod, include the `securityContext` field
in the Pod specification. The `securityContext` field is a
[PodSecurityContext](/docs/api-reference/{{page.version}}/#podsecuritycontext-v1-core) object.
[PodSecurityContext](/docs/reference/generated/kubernetes-api/{{page.version}}/#podsecuritycontext-v1-core) object.
The security settings that you specify for a Pod apply to all Containers in the Pod.
Here is a configuration file for a Pod that has a `securityContext` and an `emptyDir` volume:
@@ -131,7 +131,7 @@ exit
To specify security settings for a Container, include the `securityContext` field
in the Container manifest. The `securityContext` field is a
[SecurityContext](/docs/api-reference/{{page.version}}/#securitycontext-v1-core) object.
[SecurityContext](/docs/reference/generated/kubernetes-api/{{page.version}}/#securitycontext-v1-core) object.
Security settings that you specify for a Container apply only to
the individual Container, and they override settings made at the Pod level when
there is overlap. Container settings do not affect the Pod's Volumes.