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

Merge pull request #2169 from AdamDang/patch-11 

Typo fix: DeamonSet->DaemonSet
This commit is contained in:
k8s-ci-robot 2018-05-21 13:04:49 -07:00 committed by GitHub
parent 8f7aae4276 913d533e64
commit b8f2326860
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
contributors/design-proposals/apps/daemonset-update.md
View File

@ -42,7 +42,7 @@ Here are some potential requirements that haven't been covered by this proposal:
- Uptime is critical for each pod of a DaemonSet during an upgrade (e.g. the time - Uptime is critical for each pod of a DaemonSet during an upgrade (e.g. the time
from a DaemonSet pods being killed to recreated and healthy should be < 5s) from a DaemonSet pods being killed to recreated and healthy should be < 5s)
- Each DaemonSet pod can still fit on the node after being updated - Each DaemonSet pod can still fit on the node after being updated
- Some DaemonSets require the node to be drained before the DeamonSet's pod on it - Some DaemonSets require the node to be drained before the DaemonSet's pod on it
is updated (e.g. logging daemons) is updated (e.g. logging daemons)
- DaemonSet's pods are implicitly given higher priority than non-daemons - DaemonSet's pods are implicitly given higher priority than non-daemons
- DaemonSets can only be operated by admins (i.e. people who manage nodes) - DaemonSets can only be operated by admins (i.e. people who manage nodes)