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
We should upgrade Kubernetes to a more recent release. We're currently on v1.24.0 with the current release being v1.27.0, so we're pretty far back.
I tried upgrading to v1.24.12 as an interim step and it seemed to work: I rebuilt the Hyper-V node image and was able to deploy a new cluster successfully, or at least thought I was able to. I'm starting to wonder if the branches got mixed up and the new cluster wasn't actually upgraded.
So Kubernetes cluster initialization is failing. The first problem was that kubeadm was trying to pull containers like apiserver:1.24.12 but these images were not included in our node image. The problem here was that the neonCLOUD image publish scripts had hardcoded v1.24.0 for these containers. I fixed this by reading the Kubernetes version from the source files.
I rebuilt the container and node image and the correct image versions were there but I also saw some v1.24.13 container images and I'm not sure where those came from. Perhaps kubeadm loaded them?
I'm going to revert this change and go back to v1.24.0 for now.
The text was updated successfully, but these errors were encountered:
We should upgrade Kubernetes to a more recent release. We're currently on v1.24.0 with the current release being v1.27.0, so we're pretty far back.
I tried upgrading to v1.24.12 as an interim step and it seemed to work: I rebuilt the Hyper-V node image and was able to deploy a new cluster successfully, or at least thought I was able to. I'm starting to wonder if the branches got mixed up and the new cluster wasn't actually upgraded.
So Kubernetes cluster initialization is failing. The first problem was that kubeadm was trying to pull containers like apiserver:1.24.12 but these images were not included in our node image. The problem here was that the neonCLOUD image publish scripts had hardcoded v1.24.0 for these containers. I fixed this by reading the Kubernetes version from the source files.
I rebuilt the container and node image and the correct image versions were there but I also saw some v1.24.13 container images and I'm not sure where those came from. Perhaps kubeadm loaded them?
I'm going to revert this change and go back to v1.24.0 for now.
The text was updated successfully, but these errors were encountered: