Release v1.35.5

On Premises module release v1.35.5

Welcome to the latest release of on-premises module of SIGHUP Distribution maintained by SIGHUP by ReeVo team.

This release adds support for Kubernetes version 1.35.5, v1.34.8, v1.33.12 and updates etcd to v3.6.6, containerd to 1.7.31, and runc to 1.3.5.

Package Versions 🚢

v1.35.5

Package	Supported Version	Previous Version
etcd	3.6.6	3.5.26
haproxy	3.0	No Update
containerd	1.7.31	1.7.29
runc	1.3.5	1.3.3
kube-node-common	-	Updated
kube-control-plane	-	Updated
kube-worker	-	No update

v1.34.8

Package	Supported Version	Previous Version
etcd	3.6.6	3.5.26
haproxy	3.0	No Update
containerd	1.7.29	No update
runc	1.3.3	No update
kube-node-common	-	Updated
kube-control-plane	-	Updated
kube-worker	-	No update

v1.33.12

Package	Supported Version	Previous Version
etcd	3.6.6	3.5.26
haproxy	3.0	No Update
containerd	1.7.28	No update
runc	1.3.3	No update
kube-node-common	-	Updated
kube-control-plane	-	Updated
kube-worker	-	No update

Breaking Changes 💔

• cgroup v1 support removed: Kubernetes 1.35 removes cgroup v1 support. The kubelet will refuse to start on nodes using cgroup v1. Most modern Linux distributions already use cgroup v2 by default. Before upgrading, verify your nodes are on cgroup v2 by running stat -fc %T /sys/fs/cgroup/ , the output must be cgroup2fs. See the Kubernetes 1.35 release blog for more details.

Future Breaking Changes ⚠️

• kubeadm v1beta4 config (K8s 1.36): the on-premises installer will adopt kubeadm v1beta4 configuration starting from the next Kubernetes release (1.36). This introduces a breaking change to extraArgs: the format changes from a map to a list of {name, value} objects. If you provide custom kubeadm patches via kubeadm_patches_path, you will need to update them accordingly. See the kubeadm v1beta4 docs and the K8s 1.31 blog post for details and examples.

Bug Fixes 🐛

• [#171] Fix kubelet-csr-approver image not respecting the kubernetes_image_registry override. The manifest was a static file with a hardcoded registry.sighup.io/fury/kubelet-csr-approver:v1.0 reference. It is now a Jinja2 template that uses kubernetes_image_registry consistently with all other Kubernetes images.

New features 🌟

• [#168] Support nftables mode for kube-proxy.

Update Guide 🦮

Automatic upgrade using furyctl

To update using furyctl, follow this documentation.

Manual update

NOTE: Each on-premises environment can be different, always double-check before updating components.

1. Update SD if applicable (see the SD release notes)
2. Before upgrading to Kubernetes 1.35, ensure all etcd members are running at least v3.5.26 as required by the etcd upstream guidelines.
3. Verify all nodes are running cgroup v2 (stat -fc %T /sys/fs/cgroup/ should return cgroup2fs).
4. Update the cluster using playbooks, see the examples in this repository to know more.
5. Plan the migration to containerd 2.x before the next Kubernetes upgrade.