Diagnosing and Fixing DaemonSet Placement Across All Nodes
Scenario
A DaemonSet has been deployed in your Kubernetes cluster, but it is currently running Pods only on worker nodes.
Perform the task on the dev-machine using root user.
Tasks
- Identify why the DaemonSet Pods are not running on the control plane node.
- Update the DaemonSet manifest located at:
/root/daemonset.yamlso that Pods are scheduled on all nodes, including the control plane. - Apply the updated manifest.
Test Cases
Level up your Server Side game — Join 20,000 engineers who receive insightful learning materials straight to their inbox