Important Registry Change Information
In November, we announced that we are changing all image references from k8s.gcr.io to registry.k8s.io to keep up with the latest upstream changes. This patch release includes this change. Please ensure that any mirrors you use are able to host registry.k8s.io and/or that firewall rules are going to allow access to registry.k8s.io to pull images before upgrading to this KubeOne patch release.
The December Kubernetes patch releases (1.25.5, 1.24.9, 1.23.15, and 1.22.17) are enforcing registry.k8s.io by default. Please keep this in mind if you're using an older KubeOne patch release with the latest Kubernetes patch releases. We strongly advise that you use KubeOne v1.5.4 or newer with the latest Kubernetes patch releases.
Changelog since v1.4.11
Changes by Kind
API Change
- Image references are changed from
k8s.gcr.iotoregistry.k8s.io. This is done to keep up with the latest upstream changes. Please ensure that any mirrors you use are able to hostregistry.k8s.ioand/or that firewall rules are going to allow access toregistry.k8s.ioto pull images before applying the next KubeOne patch releases. (#2508, @xmudrii)
Feature
- KubeOne is now built using Go 1.18.9 (#2527, @xmudrii)
- Update etcd to 3.5.6 which includes a fix for the recently reported data inconsistency issue for a case when etcd crashes during processing defragmentation operation (#2500, @xmudrii)
- Enable compact hash checks as per the recommendations from etcd for detecting data corruption (#2500, @xmudrii)
- Validate support for Kubernetes patch releases 1.23.15 and 1.22.17 (#2533, @xmudrii)
Bug or Regression
- Fix a panic (NPE) when determining if it is safe to repair a cluster when there's no kubelet or kubelet systemd unit on the node (#2496, @kubermatic-bot)
- Use the pause image from
registry.k8s.iofor all Kubernetes releases (#2530, @xmudrii)