diff options
| author | Eric Paris <eparis@redhat.com> | 2015-07-20 11:45:58 -0500 |
|---|---|---|
| committer | Eric Paris <eparis@redhat.com> | 2015-07-30 20:41:30 -0400 |
| commit | 39eedfac6dd5d287611b2b21d60af7a19560aae8 (patch) | |
| tree | 1f70b00a6d13aeb7632c63ce5c54fdcd110e7020 | |
| parent | e7f04f73e8627a086bb084abb4eac4d468f4d46e (diff) | |
Rewrite how the munger works
The basic idea is that in the main mungedocs we run the entirefile and
create an annotated set of lines about that file. All mungers then act
on a struct mungeLines instead of on a bytes array. Making use of the
metadata where appropriete. Helper functions exist to make updating a
'macro block' extremely easy.
| -rw-r--r-- | security_context.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/security_context.md b/security_context.md index 03213927..8a6dd314 100644 --- a/security_context.md +++ b/security_context.md @@ -114,7 +114,7 @@ It is recommended that this design be implemented in two phases: 2. Implement a security context structure that is part of a service account. The default context provider can then be used to apply a security context based on the service account associated with the pod. - + ### Security Context Provider The Kubelet will have an interface that points to a `SecurityContextProvider`. The `SecurityContextProvider` is invoked before creating and running a given container: |