Open Ducatel opened 2 weeks ago
Automatic upgrading does not work on windows nodes. But I think we should include that in the docs or show a useful log to avoid confusion. Would you mind explaining how did you trigger the upgrade process? Thanks!
Hi,
As I said, I just follow the step from Quick start Rancher documentation and there is no place where this upgrade plan is mentioned. So I don't know at all how I can remove this schedule on windows node. After few search, It seems many peoples face this issue ( on rancher forum, stackoverflow, etc.....) without solutions.
I can probably update the node selector in the rke2-worker-plan
to avoid that, but I don't know if it's safe or not
In the RKE2 docs, we are explaining that plan: https://docs.rke2.io/upgrade/automated_upgrade
Could you be more specific about the Quick start Rancher documentation
? What exact doc are you looking at? Unfortunately, in the Quick Start Guide, I don't see anything describing upgrades:
I think we should create some anti-affinity with Windows nodes and warn the user that it needs to do that upgrade manually
I followed :
And yes, nothing about upgrade in theses documentation.
So I tried to update the plan with
matchExpressions:
- key: node-role.kubernetes.io/master
operator: DoesNotExist
- key: kubernetes.io/os
operator: NotIn
values:
- windows
But seems to not be applied
Try with this item in the matchExpressions
==> - {key: beta.kubernetes.io/os, operator: In, values: ["linux"]}
I'll probably update the docs warning about windows not being supported in the SUC and add that matchExpression in the example, so that it is less likely that people get confused
Try with this item in the
matchExpressions
==>- {key: beta.kubernetes.io/os, operator: In, values: ["linux"]}
It's not a matter of how I write the matchExpressions
. Just when I edit the plan by rancher UI or kubectl edit
my change seems to not be reflected. When I get back the yaml config, it's still the same.
I'll probably update the docs warning about windows not being supported in the SUC and add that matchExpression in the example, so that it is less likely that people get confused
The thing is, I didn't create this plan myself. So even with a documentation updated properly, some people will still face the issu
Try with this item in the
matchExpressions
==>- {key: beta.kubernetes.io/os, operator: In, values: ["linux"]}
It's not a matter of how I write the
matchExpressions
. Just when I edit the plan by rancher UI orkubectl edit
my change seems to not be reflected. When I get back the yaml config, it's still the same.I'll probably update the docs warning about windows not being supported in the SUC and add that matchExpression in the example, so that it is less likely that people get confused
The thing is, I didn't create this plan myself. So even with a documentation updated properly, some people will still face the issu
Ok, I thought this was a pure RKE2 issue but I now understand it's a Rancher issue. I'll have a look at how RM is generating that plan. I think updating the docs will also help users that are doing the upgrade by following the RKE2 docs https://docs.rke2.io/upgrade/automated_upgrade
Yeah, if this is the Rancher-managed SUC deployment and plan, then this is a Rancher issue, not RKE2.
I don't know that Rancher currently supports imported clusters with Windows nodes, I suspect it only properly handles Windows clusters that are provisioned via Rancher. I would defer to the support matrix as to whether or not this is something that is supposed to work.
Environmental Info: RKE2 Version:
On windows nodes:
On linux node:
Node(s) CPU architecture, OS, and Version:
On windows nodes:
On linux node:
Cluster Configuration:
Describe the bug:
Repeatedly observe a failing pod named apply-rke2-worker-plan* due to
ImagePullBackOff (Back-off pulling image "rancher/rke2-upgrade:v1.27.12-rke2r1")
on windows node.But pods scheduled on linux node seems to work properly.
When I tried to manually pull the image from a windows node:
So seems to not have windows compatible build.
Steps To Reproduce:
Installed RKE2:
--cni=calico
(to be able to handle windows node)On top of that, I installed rancher UI by using helm by following official documentation
Expected behavior:
Upgrade should not fail on windows node. (I don't really know what this upgrade do ???)
Actual behavior:
Upgrade fail on windows node
Thanks in advance for your help