diff options
| author | Eric Tune <etune@google.com> | 2015-07-13 11:11:34 -0700 |
|---|---|---|
| committer | Eric Tune <etune@google.com> | 2015-07-13 12:07:26 -0700 |
| commit | 8601b6ff40148c7be7a02a4a70ccfd1d9e231c33 (patch) | |
| tree | 87fbd5456d690744ff3ad0d5e234ed258d61676a | |
| parent | d4ee5006858aec1fa1fecff18bfda3dfeeb162ff (diff) | |
Remove colon from end of doc heading.
| -rw-r--r-- | secrets.md | 2 | ||||
| -rw-r--r-- | security.md | 4 |
2 files changed, 3 insertions, 3 deletions
@@ -261,7 +261,7 @@ Kubelet volume plugin API will be changed so that a volume plugin receives the s a volume along with the volume spec. This will allow volume plugins to implement setting the security context of volumes they manage. -## Community work: +## Community work Several proposals / upstream patches are notable as background for this proposal: diff --git a/security.md b/security.md index 1d1373d2..90dc3237 100644 --- a/security.md +++ b/security.md @@ -32,7 +32,7 @@ While Kubernetes today is not primarily a multi-tenant system, the long term evo ## Use cases -### Roles: +### Roles We define "user" as a unique identity accessing the Kubernetes API server, which may be a human or an automated process. Human users fall into the following categories: @@ -46,7 +46,7 @@ Automated process users fall into the following categories: 2. k8s infrastructure user - the user that kubernetes infrastructure components use to perform cluster functions with clearly defined roles -### Description of roles: +### Description of roles * Developers: * write pod specs. |