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
Linux ip-10-0-1-20 6.5.0-18-generic #18~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 7 11:40:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
3 control-planes, 2 workers
Describe the bug:
I'm not sure if it's a bug but when I move to release v1.27.11-rc1+rke2r1 (I used to be on v1.26.12+rke2r1), rke2-coredns-rke2-coredns Service name became rke2-coredns.
ConfigMap, Pods also became rke2-coredns instead of rke2-coredns-rke2-coredns.
rke2-coredns-rke2-coredns-autoscaler also rename to rke2-coredns-autoscaler.
Well, you got the idea :)
Maybe also it's the update of the rke2-coredns component as we move from 1.24.008 to 1.29.000
Sorry, I did not find more informations to determine what change this name.
Steps To Reproduce:
Installed RKE2:
Expected behavior:
Nothing special, I just want to be sure that it's something expected
Actual behavior:
Additional context / logs:
The text was updated successfully, but these errors were encountered:
Environmental Info:
RKE2 Version:
v1.27.11-rc1+rke2r1
Node(s) CPU architecture, OS, and Version:
Linux ip-10-0-1-20 6.5.0-18-generic #18~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 7 11:40:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
3 control-planes, 2 workers
Describe the bug:
I'm not sure if it's a bug but when I move to release v1.27.11-rc1+rke2r1 (I used to be on v1.26.12+rke2r1), rke2-coredns-rke2-coredns Service name became rke2-coredns.
ConfigMap, Pods also became rke2-coredns instead of rke2-coredns-rke2-coredns.
rke2-coredns-rke2-coredns-autoscaler also rename to rke2-coredns-autoscaler.
Well, you got the idea :)
Maybe also it's the update of the rke2-coredns component as we move from 1.24.008 to 1.29.000
Sorry, I did not find more informations to determine what change this name.
Steps To Reproduce:
Expected behavior:
Nothing special, I just want to be sure that it's something expected
Actual behavior:
Additional context / logs:
The text was updated successfully, but these errors were encountered: