Example Documentation: DaemonSet Node Agent
Goal
Understand how an agent Pod is run on every node using a DaemonSet.
What Is Done
The lab creates a DaemonSet that starts a BusyBox agent on every matching node and prints node information through the Downward API.
Typical Commands
kubectl apply -f manifests/
kubectl rollout status daemonset/node-agent -n daemonset-lab
kubectl get pods -n daemonset-lab -o wide
kubectl logs -n daemonset-lab -l app=node-agent --tail=20
Validate Success
- One agent Pod runs per node.
- Logs contain Pod and node names.
- Resource limits and securityContext are set.
Common Mistakes
- Control-plane taints are not considered.
- Agents receive overly broad permissions.
- DaemonSet updates are interpreted like Deployment rollouts.