Difference between revisions of "Kubernetes DaemonSets"
Jump to navigation
Jump to search
Line 14: | Line 14: | ||
== Activities == | == Activities == | ||
* [[CKA v1.18]]: [[Understand the role of DaemonSets]] | * [[CKA v1.18]]: [[Understand the role of DaemonSets]] | ||
− | * Stop | + | * Stop DaemonSet: <code>[[kubectl patch]] daemonset <name-of-daemon-set> -p '{"spec": {"template": {"spec": {"nodeSelector": {"non-existing": "true"}}}}}'</code> |
== Related terms == | == Related terms == |
Revision as of 13:29, 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-resources
kind: DaemonSet
kubectl get daemonset, kubectl get daemonset -A
kubectl rollout daemonset
- StatefulSet
- aws-node
See also
Advertising: