Difference between revisions of "Kubernetes DaemonSets"
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
* <code>[[kubectl rollout daemonset]]</code> | * <code>[[kubectl rollout daemonset]]</code> | ||
* [[StatefulSet]] | * [[StatefulSet]] | ||
| − | * [[aws-node]] | + | * [[aws-node]]: <code>[[kubectl -n kube-system edit daemonset/aws-node]]</code> |
== See also == | == See also == | ||
Revision as of 14:22, 22 February 2024
Kubernetes Daemonset can be used to run replicas of a pod on specific or all nodes.
- https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/
- https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/#daemonset
Typical uses of a DaemonSet are:
- Running a cluster storage daemon on every node
- Running a logs collection daemon on every node
- Running a node monitoring daemon on every node
Official example
https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/
Activities
- CKA v1.18: Understand the role of DaemonSets
- Stop DaemonSet:
kubectl patch daemonset <name-of-daemon-set> -p '{"spec": {"template": {"spec": {"nodeSelector": {"non-existing": "true"}}}}}'
Related terms
kubectl api-resourceskind: DaemonSetkubectl get daemonset, kubectl get daemonset -Akubectl rollout daemonset- StatefulSet
- aws-node:
kubectl -n kube-system edit daemonset/aws-node
See also
Advertising:
