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.
This commit is contained in:
Eric Paris
2015-07-20 11:45:58 -05:00
parent 4cbca2e63c
commit 8886a9940d
22 changed files with 758 additions and 512 deletions

View File

@@ -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: