Describe the bug
In latest rke2 version 1.29.x , kube-scheduler component config (KubeSchedulerConfiguration) kubescheduler.config.k8s.io/v1beta3 is removed.
Due to which while addons deployment csi baremetal pods were not up as kube-scheduler pods are in the CLBO state.
CSI Pod Error:-
Events:
Type Reason Age From Message
Normal Scheduled 28m default-scheduler Successfully assigned atlantic/csi-baremetal-se-fgxsc to master2
Normal Pulled 28m kubelet Container image "dockerrepo:30500/csi-baremetal-scheduler-extender:1.6.0-669.aa032e6" already present on machine
Normal Created 28m kubelet Created container scheduler-extender
Normal Started 28m kubelet Started container scheduler-extender
Warning Unhealthy 3m23s (x190 over 28m) kubelet Readiness probe failed: error: health rpc failed: rpc error: code = Unknown desc = kube-scheduler kube-scheduler-master2 is not restarted after patching
kube-scheduler pod Error :-
master1:~ # kubectl logs kube-scheduler-master1 -n kube-system
I0312 11:13:23.801281 1 serving.go:380] Generated self-signed cert in-memory
E0312 11:13:23.804099 1 run.go:74] "command failed" err="no kind \"KubeSchedulerConfiguration\" is registered for version \"kubescheduler.config.k8s.io/v1beta3\" in scheme \"kubernetes/pkg/scheduler/apis/config/scheme/scheme.go:29\""
Environment (please complete the following information):
All
To Reproduce
Steps to reproduce the behavior.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Describe the bug In latest rke2 version 1.29.x , kube-scheduler component config (KubeSchedulerConfiguration) kubescheduler.config.k8s.io/v1beta3 is removed.
Due to which while addons deployment csi baremetal pods were not up as kube-scheduler pods are in the CLBO state.
CSI Pod Error:-
Events: Type Reason Age From Message
Normal Scheduled 28m default-scheduler Successfully assigned atlantic/csi-baremetal-se-fgxsc to master2 Normal Pulled 28m kubelet Container image "dockerrepo:30500/csi-baremetal-scheduler-extender:1.6.0-669.aa032e6" already present on machine Normal Created 28m kubelet Created container scheduler-extender Normal Started 28m kubelet Started container scheduler-extender Warning Unhealthy 3m23s (x190 over 28m) kubelet Readiness probe failed: error: health rpc failed: rpc error: code = Unknown desc = kube-scheduler kube-scheduler-master2 is not restarted after patching
kube-scheduler pod Error :-
master1:~ # kubectl logs kube-scheduler-master1 -n kube-system I0312 11:13:23.801281 1 serving.go:380] Generated self-signed cert in-memory E0312 11:13:23.804099 1 run.go:74] "command failed" err="no kind \"KubeSchedulerConfiguration\" is registered for version \"kubescheduler.config.k8s.io/v1beta3\" in scheme \"kubernetes/pkg/scheduler/apis/config/scheme/scheme.go:29\""
Environment (please complete the following information):
To Reproduce Steps to reproduce the behavior.
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.