2ded739ec1
* Update DaemonSet deletion documentation The "Updating a DaemonSet" section referred to pre-1.6 behavior, where rolling updates of DaemonSets were not supported and thus orphaned pods from deleted DaemonSets would not be replaced by a new DaemonSet. Describe the new behavior, where orphaned pods can be adopted by a new DaemonSet and may be replaced depending on the update strategy in use. * Tweak language around Pod replacement after DaemonSet deletion * Update note about DaemonSet rolling updates No need to call out the version in which rolling updates for DaemonSets were introduced given how long they've been supported. |
||
|---|---|---|
| .. | ||
| architecture | ||
| cluster-administration | ||
| configuration | ||
| containers | ||
| extend-kubernetes | ||
| overview | ||
| policy | ||
| scheduling | ||
| security | ||
| services-networking | ||
| storage | ||
| workloads | ||
| _index.md | ||
| example-concept-template.md | ||