From ea53fd7697e3e94d155d83a543359d1ef4433912 Mon Sep 17 00:00:00 2001 From: Adam Pyle Date: Mon, 25 Apr 2016 09:18:26 +1000 Subject: [PATCH] Incorrect attribute - docs - pod-security-context Pod definition had incorrect spelling on attribute `securityContext` Also fixed the flow of Motivation intro paragraph. --- docs/proposals/pod-security-context.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/proposals/pod-security-context.md b/docs/proposals/pod-security-context.md index 420a006e686..2899515cdc2 100644 --- a/docs/proposals/pod-security-context.md +++ b/docs/proposals/pod-security-context.md @@ -40,7 +40,7 @@ order to correctly model pod- and container-level security concerns. ## Motivation Currently, containers have a `SecurityContext` attribute which contains information about the -security settings the container uses. In practice many of these attributes are uniform across all +security settings the container uses. In practice, many of these attributes are uniform across all containers in a pod. Simultaneously, there is also a need to apply the security context pattern at the pod level to correctly model security attributes that apply only at a pod level. @@ -277,7 +277,7 @@ to implement, explain, and support. Instead, we will approach backward compatib securityContext: runAsUser: 1001 - name: b - securityContest: + securityContext: runAsUser: 1002 ```