Perform a Rolling Update on a DaemonSet
Kubernetes Docs · نسخهٔ f284a9e7c87f · CC BY 4.0 برای مستندات و مجوزهای همراه
<!-- overview --> This page shows how to perform a rolling update on a DaemonSet.
{{% heading "prerequisites" %}}
{{< include "task-tutorial-prereqs.md" >}}
<!-- steps -->
DaemonSet Update Strategy
DaemonSet has two update strategy types:
OnDelete: WithOnDeleteupdate strategy, after you update a DaemonSet template, new
DaemonSet pods will *only* be created when you manually delete old DaemonSet pods. This is the same behavior of DaemonSet in Kubernetes version 1.5 or before.
RollingUpdate: This is the default update strategy.
With RollingUpdate update strategy, after you update a DaemonSet template, old DaemonSet pods will be killed, and new DaemonSet pods will be created automatically, in a controlled fashion. At most one pod of the DaemonSet will be running on each node during the whole update process.
Performing a Rolling Update
To enable the rolling update feature of a DaemonSet, you must set its .spec.updateStrategy.type to RollingUpdate.
You may want to set [.spec.updateStrategy.rollingUpdate.maxUnavailable](/docs/reference/kubernetes-api/workload-resources/daemon-set-v1/#DaemonSetSpec) (default to 1), [.spec.minReadySeconds](/docs/reference/kubernetes-api/workload-resources/daemon-set-v1/#DaemonSetSpec) (default to 0) and [.spec.updateStrategy.rollingUpdate.maxSurge](/docs/reference/kubernetes-api/workload-resources/daemon-set-v1/#DaemonSetSpec) (defaults to 0) as well.
Creating a DaemonSet with RollingUpdate update strategy
This YAML file specifies a DaemonSet with an update strategy as 'RollingUpdate'
{{% code_sample file="controllers/fluentd-daemonset.yaml" %}}
After verifying the update strategy of the DaemonSet manifest, create the DaemonSet:
kubectl create -f https://k8s.io/examples/controllers/fluentd-daemonset.yamlAlternatively, use kubectl apply to create the same DaemonSet if you plan to update the DaemonSet with kubectl apply.
kubectl apply -f https://k8s.io/examples/controllers/fluentd-daemonset.yamlChecking DaemonSet RollingUpdate update strategy
Check the update strategy of your DaemonSet, and make sure it's set to RollingUpdate:
kubectl get ds/fluentd-elasticsearch -o go-template='{{.spec.updateStrategy.type}}{{"\n"}}' -n kube-systemIf you haven't created the DaemonSet in the system, check your DaemonSet manifest with the following command instead:
kubectl apply -f https://k8s.io/examples/controllers/fluentd-daemonset.yaml --dry-run=client -o go-template='{{.spec.updateStrategy.type}}{{"\n"}}'The output from both commands should be:
RollingUpdateIf the output isn't RollingUpdate, go back and modify the DaemonSet object or manifest accordingly.
Updating a DaemonSet template
Any updates to a RollingUpdate DaemonSet .spec.template will trigger a rolling update. Let's update the DaemonSet by applying a new YAML file. This can be done with several different kubectl commands.
{{% code_sample file="controllers/fluentd-daemonset-update.yaml" %}}
Declarative commands
If you update DaemonSets using configuration files, use kubectl apply:
kubectl apply -f https://k8s.io/examples/controllers/fluentd-daemonset-update.yamlImperative commands
If you update DaemonSets using imperative commands, use kubectl edit :
kubectl edit ds/fluentd-elasticsearch -n kube-system##### Updating only the container image
If you only need to update the container image in the DaemonSet template, i.e. .spec.template.spec.containers[*].image, use kubectl set image:
kubectl set image ds/fluentd-elasticsearch fluentd-elasticsearch=quay.io/fluentd_elasticsearch/fluentd:v2.6.0 -n kube-systemWatching the rolling update status
Finally, watch the rollout status of the latest DaemonSet rolling update:
kubectl rollout status ds/fluentd-elasticsearch -n kube-systemWhen the rollout is complete, the output is similar to this:
daemonset "fluentd-elasticsearch" successfully rolled outTroubleshooting
DaemonSet rolling update is stuck
Sometimes, a DaemonSet rolling update may be stuck. Here are some possible causes:
Some nodes run out of resources
The rollout is stuck because new DaemonSet pods can't be scheduled on at least one node. This is possible when the node is running out of resources.
When this happens, find the nodes that don't have the DaemonSet pods scheduled on by comparing the output of kubectl get nodes and the output of:
kubectl get pods -l name=fluentd-elasticsearch -o wide -n kube-systemOnce you've found those nodes, delete some non-DaemonSet pods from the node to make room for new DaemonSet pods.
{{< note >}} This will cause service disruption when deleted pods are not controlled by any controllers or pods are not replicated. This does not respect PodDisruptionBudget either. {{< /note >}}
Broken rollout
If the recent DaemonSet template update is broken, for example, the container is crash looping, or the container image doesn't exist (often due to a typo), DaemonSet rollout won't progress.
To fix this, update the DaemonSet template again. New rollout won't be blocked by previous unhealthy rollouts.
Clock skew
If .spec.minReadySeconds is specified in the DaemonSet, clock skew between master and nodes will make DaemonSet unable to detect the right rollout progress.
Clean up
Delete DaemonSet from a namespace :
kubectl delete ds fluentd-elasticsearch -n kube-system{{% heading "whatsnext" %}}
- See Performing a rollback on a DaemonSet
- See Creating a DaemonSet to adopt existing DaemonSet pods