From 89f07696502886a0670245c0e3bef3bf1296fbca Mon Sep 17 00:00:00 2001 From: Martin Mosegaard Amdisen Date: Mon, 12 Feb 2018 23:05:50 +0100 Subject: [PATCH] Update security-context.md (#7366) * 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 --- docs/tasks/configure-pod-container/security-context.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tasks/configure-pod-container/security-context.md b/docs/tasks/configure-pod-container/security-context.md index 4559c83105..55781022a5 100644 --- a/docs/tasks/configure-pod-container/security-context.md +++ b/docs/tasks/configure-pod-container/security-context.md @@ -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.