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
This was validated previously on v1.21.x in rancher. Rancher does not currently support 1.22. I have validated that externalIp is working in a standalone setting for windows agents using v1.22.2-rc1+rke2r1:
$ gimme
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
node/ec2amaz-84s9eu2 Ready <none> 35s v1.22.2 172.31.31.102 <redacted> Windows Server 2022 Datacenter 10.0.20348.230 containerd://1.5.7
node/ip-172-31-18-55 Ready control-plane,etcd,master 59m v1.22.2+rke2r1 172.31.18.55 <redacted> Ubuntu 20.04.2 LTS 5.4.0-1045-aws containerd://1.5.7-k3s1
node/ip-ac1f16e9 Ready <none> 29m v1.22.2 172.31.22.233 <none> Windows Server 2019 Datacenter 10.0.17763.2061 containerd://1.5.7
Environmental Info:
RKE2 Version:
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
1 Server
1 Window agent
Describe the bug:
See the following GH Issue: rancher/windows#91
Steps To Reproduce:
Register the windows node with the -Address command.
Expected behavior:
External IP should display in dashboard
Actual behavior:
External IP isn't registered and doesn't display correctly.
Additional context / logs:
The text was updated successfully, but these errors were encountered: