-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[windows rke2] can't deploy wins-upgrader on windows 2022 cluster #37020
Comments
@luthermonson what we talked about offline, https://github.com/rancher/wins/blob/f4b33a072aa08d3dc5b4af3ed25a5b15b5a1c55d/charts/rancher-wins-upgrader/scripts/upgrade.ps1#L53 should be set correctly for RKE2 since wins is no longer placed in |
@aiyengar2 @luthermonson @slickwarren we don't need this functionality for RKE2. Wins is the system agent and needs to upgrade using the system agent upgrader. |
the system agent upgrade process needs to line up with the wins upgrade process as wins is the windows system agent in rke2. per @slickwarren the upgrade process for system agent is to upgrade rancher to confirm new versions. we need to validate that process works for wins and open another issue against the v2prov upgrade process. the wins-upgrader will need to be designated an rke1 only solution and this issue is probably closable. |
Since we aren't going to support wins-upgrader on RKE2 and RKE1 for Windows is end of life, I am going to close this issue. /cc @snasovich |
Work for supporting wins (windows system agent) upgrades for RKE2 is being handled here: rancher/windows#181 |
Rancher Server Setup
Information about the Cluster
Describe the bug
wins-upgrader does deploy, but the daemonset does not successfully deploy and continuously goes into
crashloopbackoff
stateTo Reproduce
Result
Expected Result
winsupgrader should deploy and all pods from deployment should get to an active state.
Additional context
The text was updated successfully, but these errors were encountered: