-
Notifications
You must be signed in to change notification settings - Fork 228
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
[SURE-5515] Fleet is not upgrading properly on windows nodes in a cluster with windows workers #993
Comments
still reproducible on v2.7.2-rc7 |
See rancher/rancher#39372 (comment) for more details |
So this deployment doesn't schedule on Windows:
But https://github.com/rancher/fleet/blob/master/pkg/agent/manifest.go#L178-L209 does. How do we fix this, do we just add the
Adding to affinity could also be done as a workaround via the cluster config. |
Additionnal QAProblemUsing fleet in an environment with mixed nodes (linux+windows), would show failures for the windows nodes. Fleet agent cannot run on windows. SolutionAdding a TestingEngineering TestingManual TestingI don't have access to a cluster with windows nodes. Automated TestingQA Testing ConsiderationsFleet should still start on the linux nodes. Regressions Considerations |
This is my observation: I see no |
Is there an existing issue for this?
Current Behavior
After upgrading rancher with an existing cluster that is running rke2 with a windows node from 2.6.8 -> 2.6.9-rc1, (fleet v0.3.11 -> v0.4.0-rc3) , fleet fails to upgrade as it is consistently trying to run on the windows node.
Expected Behavior
Expecting fleet to work in a windows cluster after upgrade
Steps To Reproduce
Environment
Logs
Anything else?
No response
The text was updated successfully, but these errors were encountered: