kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix misspelled word `overriden` to `overridden`

This commit is contained in:
Xingcai Zhang 2017-10-22 15:01:28 +08:00
parent ff637fb531
commit e4a0208c84
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
contributors/design-proposals/apps/stateful-apps.md
View File

@ -346,7 +346,7 @@ Requested features:
* Jobs can be used to perform a run-once initialization of the cluster
* Init containers can be used to prime PVs and config with the identity of the pod.
* Templates and how fields are overriden in the resulting object should have broad alignment
* Templates and how fields are overridden in the resulting object should have broad alignment
* DaemonSet defines the core model for how new controllers sit alongside replication controller and
how upgrades can be implemented outside of Deployment objects.

2
contributors/design-proposals/auth/runas-groupid.md
View File

@ -11,7 +11,7 @@ As a Kubernetes User, we should be able to specify both user id and group id for
inside a pod on a per Container basis, similar to how docker allows that using docker run options `-u,
--user="" Username or UID (format: <name|uid>[:<group|gid>]) format`.
PodSecurityContext allows Kubernetes users to specify RunAsUser which can be overriden by RunAsUser
PodSecurityContext allows Kubernetes users to specify RunAsUser which can be overridden by RunAsUser
in SecurityContext on a per Container basis. There is no equivalent field for specifying the primary
Group of the running container.