-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Linux tolerations for all deployments #324
Comments
I have a windows cluster, but no windows nodes yet. Have 1 etcd+control and 3 worker nodes linux nodes. No windows nodes.
Expected: |
#323 has been merged, but we should get a newly tagged chart into |
A new chart has been tagged: |
Successfully validated the fix. HA upstream cluster based on rancher:v2.5-head After bootstraping a downstream windows cluster (flannel,VXLAN), with 3 linux nodes only (same roles - etcd, control, worker), I see there is one Running/Active replica of fleet-agent pod using The issue is reproducible on rancher:2.5.7 with rancher/fleet:v0.3.4 - the fleet-agent pod on downstream windows cluster (only linux nodes) is not running and failing on:
|
Reopening for a check on master-head in |
Blocked by broken Cluster Explorer in master-head |
Blocked because of this issue - rancher/rancher#31964 |
Closing this, tracking master-head validation here - #339 |
With a "Windows cluster", there may not actually be any Windows node in a "Ready" state yet. In case pods have to fall back to Linux nodes, they need to toleration to do so.
Discovered by @sowmyav27
The text was updated successfully, but these errors were encountered: