The chart doesn't allow modifying the deployment affinity rules. Thus, if running multiple instances, there is no option to encourage or force them onto different nodes using anti-affinity.
A podDisruptionBudget would also help protect this failure scenario, which is also unavailable...
The chart doesn't allow modifying the deployment affinity rules. Thus, if running multiple instances, there is no option to encourage or force them onto different nodes using anti-affinity.
A podDisruptionBudget would also help protect this failure scenario, which is also unavailable...