From a8465ce1f0b13dc6e03d0ec3bac5fef6a06b57d5 Mon Sep 17 00:00:00 2001 From: Xiaoyu Zhang Date: Thu, 30 Mar 2017 18:51:07 +0800 Subject: [PATCH] Update links from v1.5 to v1.6 Update links from v1.5 to v1.6 --- docs/concepts/policy/container-capabilities.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/concepts/policy/container-capabilities.md b/docs/concepts/policy/container-capabilities.md index c3c3da3e05..70019a61cf 100644 --- a/docs/concepts/policy/container-capabilities.md +++ b/docs/concepts/policy/container-capabilities.md @@ -63,7 +63,7 @@ This table shows the relationship between Docker capabilities and | BLOCK_SUSPEND | CAP_BLOCK_SUSPEND | In Kubernetes, you can add or drop capabilities in the -[`SecurityContext`](/docs/resources-reference/v1.5/#securitycontext-v1) +[`SecurityContext`](/docs/resources-reference/v1.6/#securitycontext-v1-core) field of a Container: ```yaml @@ -92,7 +92,7 @@ spec: * [Pod Security Policy](/docs/user-guide/pod-security-policy/) -* [SecurityContext](/docs/resources-reference/v1.5/#securitycontext-v1) +* [SecurityContext](/docs/resources-reference/v1.6/#securitycontext-v1-core) * [Container](/docs/api-reference/v1.6/#container-v1-core)