Difference between revisions of "Kubernetes DaemonSets"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
|||
Line 17: | Line 17: | ||
* <code>[[kubectl api-resources]]</code> | * <code>[[kubectl api-resources]]</code> | ||
* <code>[[kind]]: DaemonSet</code> | * <code>[[kind]]: DaemonSet</code> | ||
+ | * <code>[[kubectl get daemonset]]</code> | ||
* [[StatefulSet]] | * [[StatefulSet]] | ||
Revision as of 18:35, 11 June 2022
Daemonset can be used to run replicas of a pod on specific or all node
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
Activities
- CKA v1.18: Understand the role of DaemonSets
Related terms
See also
- Kubernetes Workloads:
Deployment
,ReplicaSet, StatefulSet, DaemonSets, Job, CronJob
,.apps/
- Kubernetes: distributions, tools, CKA, CKS, Kubernetes interfaces: CSI, CNI, installation, workloads, networking,
kubeadm
,Kubernetes API
, Kubernetes API Server,kubectl, kubeadm, kubelet, kube-proxy
, Cloud services: EKS, GKE, TKE, DKS, Helm, Kubernetes RBAC, Kubernetes deployments, Minikube, Rancher, OpenShift, Charmed Kubernetes, Ingress, Kubernetes scheduler, Kubernetes Finalizers, logging, Kubernetes operator, Orka,kind:
, Kubernetes namespaces, Kubernetes dashboard, Kubernetes Metrics Server, Field Selectors, CoreDNS, CRI, Kubernetes Topology Manager, Kubernetes governance: (SIG, KEP), Kustomize, controllers,ReadinessProbe, LivenessProbe
, KOPS, K9s, Kui, k3s, ImagePullBackOff, PDB, EndPoints, Kots, metadata, Karpenter, Replicated.com, Kubernetes Authenticating, Kubernetes timeline, Changelog/Versions, service accounts, Kubernetes Pod Lifecycle, Kubernetes Conformance Certified, Kubernetes backup, Kubernetes Pod Security Admission, tEKS, Kubernetes events, Kubernetes ports, Kubernetes policies, Connect, addons, DoKC, Kubernetes control plane, Kubernetes Federation, Kubernetes info, Kubetest2, Sidecar (Kubernetes)
Advertising: