Difference between revisions of "Kubernetes DaemonSets"
Jump to navigation
Jump to search
(3 intermediate revisions by the same user not shown) | |||
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 == | ||
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> |
+ | * <code>[[kubectl describe ds]]</code> | ||
== See also == | == See also == |
Latest revision as of 10:49, 28 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[edit]
https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/
Activities[edit]
- 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[edit]
kubectl api-resources
kind: DaemonSet
kubectl get daemonset, kubectl get daemonset -A
kubectl rollout daemonset
- StatefulSet
- aws-node:
kubectl -n kube-system edit daemonset/aws-node
kubectl describe ds
See also[edit]
Advertising: