I've been digging into how DaemonSets and static pods function within Kubernetes, particularly on OpenShift clusters. My understanding is that these components need to be present on every node for everything to run smoothly. However, I think they should include tolerations for all types of taints, or vendors should ensure this capability is available. I'm specifically looking at DaemonSets like `iptables-alerter` and `ingress-canary`. I don't have a Red Hat subscription, so any insights would be really appreciated!
2 Answers
I get where you're coming from! You want to restrict certain pods to specific nodes based on taints. DaemonSets and static pods are designed for specific functions and don't necessarily need tolerations unless you're placing restrictions on them. Many times, they serve a functional role across all nodes, but their necessity can vary.
The purpose of the taint toleration system is to control which pods can run on which nodes. Tolerations allow pods to be scheduled onto nodes even if they have taints. Not all pods, like DaemonSets or static pods, necessarily need tolerations, but it's important they do if they should operate on tainted nodes.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures