Release Proposal v2.29.1

[tico88612]

Changes by Kind

Bug or Regression

• Fix Calico apiserver RBAC permissions for Kubernetes 1.33+ ([release-2.29] Update Calico apiserver RBAC for Kubernetes 1.33+ #12695, @k8s-infra-cherrypick-robot)
• Fix Cilium loadBalancer.mode rendering in Kubespray values template. ([release-2.29] Fix Cilium loadBalancer.mode rendering in Kubespray template #12705, @k8s-infra-cherrypick-robot)
• Fix(calico): Add missed rbac verb watch for hostendpoints ([release-2.29] fix(calico): Add missed rbac verb watch for hostendpoints #12644, @k8s-infra-cherrypick-robot)
• Removing external etcd member (not stacked with control plane) should now work without erroring out because the node is not in the kubernetes cluster ([release-2.29] Remove etcd member by peerURLs #12685, @k8s-infra-cherrypick-robot)

Components

• kubernetes 1.33.6
• etcd 3.5.25
• docker 28.3
• containerd 2.1.5
• cri-o 1.33.7
• cni-plugins 1.8.0
• calico 3.30.5
• cilium 1.18.4
• flannel 0.27.3
• kube-ovn 1.12.21
• kube-router 2.1.1
• multus 4.2.2
• kube-vip 0.8.0
• cert-manager 1.15.3
• coredns 1.12.0
• ingress-nginx 1.13.3
• argocd 2.14.5
• helm 3.18.4
• metallb 0.13.9
• registry 2.8.1
• aws-ebs-csi-plugin 0.5.0
• azure-csi-plugin 1.10.0
• cinder-csi-plugin 1.30.0
• gcp-pd-csi-plugin 1.9.2
• local-path-provisioner 0.0.32
• local-volume-provisioner 2.5.0
• node-feature-discovery 0.16.4

[tico88612]

Hi approvers, could anyone take a look at this? Do we have any PR that needs to be blocked?

cc @VannTen @ant31 @yankay @mzaian

[VannTen]

I haven't seen any egregious regression in the issues or PR, so good for me. I'll shout if I see anything, as I'm reviewing while waiting for my control plane to rotate to RHEL9 😴 (it's not fast 😝 )

[xin053]

Hi, could this PR(#12627) backport to v2.29.1 Thx.

[yankay]

It's /lgtm , thanks @tico88612

[tico88612]

Hi, could this PR(#12627) backport to v2.29.1 Thx.

Not sure what the risk when we bump CSI major version? 🤔
Do you have any thoughts about this?

[tico88612]

BTW, v2.30.0 will coming soon after the K8s 1.35.0 released.

[xin053]

Hi, could this PR(#12627) backport to v2.29.1 Thx.

Not sure what the risk when we bump CSI major version? 🤔 Do you have any thoughts about this?

You are right，currently AWS, GCP and Cinder CSI rely on csi_**_tag that make csi update a bit risky，sorry I don't hava aws or gcp environment to test，I only test cinder csi which work fine.

[VannTen]

IMO we should avoid backporting the CSI stuff:

• it's not a regression in 2.29.0
• major version bump.

[tico88612]

/assign

I'll release v2.29.1 this week.