diff options
| author | Tamer Tas <tamertas@outlook.com> | 2015-04-01 01:18:49 +0300 |
|---|---|---|
| committer | Tamer Tas <tamertas@outlook.com> | 2015-04-01 01:18:49 +0300 |
| commit | f08e73cb56a68974b3be06c97bce7ec8dab1c786 (patch) | |
| tree | 4074444a3d0c897bd1835d1607d5c9df8b258200 /secrets.md | |
| parent | 2108ead7d3ed6cdcea54aa73e6fb913010d7849c (diff) | |
Fix typo in Secrets design document
Diffstat (limited to 'secrets.md')
| -rw-r--r-- | secrets.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -21,7 +21,7 @@ Goals of this design: ## Constraints and Assumptions * This design does not prescribe a method for storing secrets; storage of secrets should be - pluggable to accomodate different use-cases + pluggable to accommodate different use-cases * Encryption of secret data and node security are orthogonal concerns * It is assumed that node and master are secure and that compromising their security could also compromise secrets: @@ -375,7 +375,7 @@ a tmpfs file system of that size to store secret data. Rough accounting of spec For use-cases where the Kubelet's behavior is affected by the secrets associated with a pod's `ServiceAccount`, the Kubelet will need to be changed. For example, if secrets of type `docker-reg-auth` affect how the pod's images are pulled, the Kubelet will need to be changed -to accomodate this. Subsequent proposals can address this on a type-by-type basis. +to accommodate this. Subsequent proposals can address this on a type-by-type basis. ## Examples |
