This message was deleted.

Hello vasili....i think the first thing is to check the compatibility of your workload to new version of kubernetes...then you need to check whether the current rke binary support the new version..if not you need to download the new rke which support the desired k8s binary....after that just change the kubernetes version in cluster.yaml and do the rke up......again the most important part is to check the compatibility of your current workload..for example check if your cni does not have any problem with desired k8s version...good luck

yes i try everything like that but when i try to upgrade i got this error: ERRO[0147] Failed to upgrade hosts: rke01 with error [Failed to verify healthcheck: Failed to check https://localhost:6443/healthz for service [kube-apiserver] on host [10.63.0.11]: Get "https://localhost:6443/healthz": Unable to access the service on localhost:6443. The service might be still starting up. Error: ssh: rejected: connect failed (Connection refused), log: E0716 141253.805223 1 run.go:74] "command failed" err="failed to initialize admission: couldn't init admission plugin \"PodSecurity\": no kind \"PodSecurityConfiguration\" is registered for version \"pod-security.admission.config.k8s.io/v1\" in scheme \"vendor/k8s.io/pod-security-admission/admission/api/scheme/scheme.go:30\""] FATA[0147] [controlPlane] Failed to upgrade Control Plane: [[Failed to verify healthcheck: Failed to check https://localhost:6443/healthz for service [kube-apiserver] on host [10.63.0.11]: Get "https://localhost:6443/healthz": Unable to access the service on localhost:6443. The service might be still starting up. Error: ssh: rejected: connect failed (Connection refused), log: E0716 141253.805223 1 run.go:74] "command failed" err="failed to initialize admission: couldn't init admission plugin \"PodSecurity\": no kind \"PodSecurityConfiguration\" is registered for version \"pod-security.admission.config.k8s.io/v1\" in scheme \"vendor/k8s.io/pod-security-admission/admission/api/scheme/scheme.go:30\""]] in cluster.yml pod_security_policy: false