You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Installing Fleet charts in a cluster where all nodes are tainted would fail, because Fleet jobs did not support node tolerations coming from chart values. This would result in Fleet failing to install.
Affected jobs were the cleanup jobs for cluster registrations and completed jobs.
Solution
The Fleet chart now propagates node tolerations from chart values to those jobs, as it does for other deployed pods.
Testing
Engineering Testing
Manual Testing
This has been tested by tainting one node in a k3d cluster, and checking that:
deployment was successful
jobs were not scheduled on the tainted node, unless the corresponding toleration was set in chart values
Automated Testing
N/A
QA Testing Considerations
It would make sense to test this in a cluster where all nodes are tainted:
if no tolerations are specified in chart values, running the above mentioned jobs should still fail
setting tolerations matching at least one node's taints should enable successful deployment, with both jobs being created and run successfully.
Forward-port of #3180 to v0.12.
The text was updated successfully, but these errors were encountered: