Ensure tainted nodes are updated
When you deploy or upgrade the Logging agent, you can configure the logs-values.yaml file to include information on what to do when you have tainted nodes.
For example, if you have a taint on a node: kubectl taint nodes 10.1.2.3 myNodeType=ingress:NoSchedule, you can configure the agent to be scheduled on that node by adding the tolerations configuration to your log-values.yaml file:
tolerations:
- effect: NoSchedule
key: myNodeType
value: ingress
operator: Equal
- These fields are directly added to the DaemonSet's tolerations section.
- This ensures the agent respects the taint rules and can be scheduled accordingly.
After you modify the logs-values.yaml, you can Upgrade the agent or continue modifying the file before applying all the changes.