.png)
How It Works
When you create a DaemonSet, Kubernetes schedules a copy of the designated pod on each node in the cluster. As new nodes join, the DaemonSet pod deploys to them automatically. When a node is removed, its DaemonSet pod is cleaned up without manual intervention. Common uses include log collectors, monitoring agents, and security scanners that need to run on every machine in the cluster. Unlike a standard Deployment, which targets a replica count, a DaemonSet targets node coverage.
Why It Matters for Cloud Cost
DaemonSets add baseline resource consumption to every node, and that cost compounds as clusters scale. Each DaemonSet pod requests CPU and memory, which reduces the capacity available for workload pods and can force Kubernetes to provision additional nodes sooner than necessary. Teams that run multiple DaemonSets without reviewing their resource requests often pay for more compute than their applications actually require. Right-sizing DaemonSet pods and auditing which ones are truly necessary are standard steps in Kubernetes cost optimization.
Usage AI’s Flex Savings Plan covers the EC2 and Fargate compute that Kubernetes clusters run on, saving 40 to 60% versus on-demand pricing.