Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typo in /docs/design/secrets.md #6250

Merged
merged 1 commit into from
Mar 31, 2015
Merged

Fix typo in /docs/design/secrets.md #6250

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/design/secrets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down Expand Up @@ -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

Expand Down