diff options
| author | AdamDang <adam.dang@daocloud.io> | 2018-05-21 23:09:52 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-05-21 23:09:52 +0800 |
| commit | 913d533e649d651cf8c6fde209ce5cd642d4b3db (patch) | |
| tree | 6e7efc83013e8f5221aee096424c49042c89844d | |
| parent | 8f7aae4276860c4984f4ff11c231d68929ed15f7 (diff) | |
Typo fix: DeamonSet->DaemonSet
| -rw-r--r-- | contributors/design-proposals/apps/daemonset-update.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/apps/daemonset-update.md b/contributors/design-proposals/apps/daemonset-update.md index aea7e244..f4ce1256 100644 --- a/contributors/design-proposals/apps/daemonset-update.md +++ b/contributors/design-proposals/apps/daemonset-update.md @@ -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 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 -- 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) - DaemonSet's pods are implicitly given higher priority than non-daemons - DaemonSets can only be operated by admins (i.e. people who manage nodes) |