From 4c504ad0afbedfc78078e9a44e51ca1a823e505a Mon Sep 17 00:00:00 2001 From: Ricky Pai Date: Thu, 25 Aug 2016 17:07:26 -0700 Subject: [PATCH] Use different anchor for better navigation the anchor `#use-case-two-containers` will jump the page where the title is not visible, so it's hard to understand the context. `#use-case-secret-visible-to-one-container-in-a-pod` is a better anchor choice since it jumps straight to the title so the context is clear. --- docs/user-guide/secrets/index.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/user-guide/secrets/index.md b/docs/user-guide/secrets/index.md index 6cf073d828..9c348a07fb 100644 --- a/docs/user-guide/secrets/index.md +++ b/docs/user-guide/secrets/index.md @@ -642,8 +642,6 @@ you must use `ls -la` to see them when listing directory contents. ### Use-case: Secret visible to one container in a pod - - Consider a program that needs to handle HTTP requests, do some complex business logic, and then sign some messages with an HMAC. Because it has complex application logic, there might be an unnoticed remote file reading exploit in @@ -688,7 +686,7 @@ Therefore, one Pod does not have access to the secrets of another pod. There may be several containers in a pod. However, each container in a pod has to request the secret volume in its `volumeMounts` for it to be visible within the container. This can be used to construct useful [security partitions at the -Pod level](#use-case-two-containers). +Pod level](#use-case-secret-visible-to-one-container-in-a-pod). ### Risks