ZeroDownTime/KubeZero
3
0
Fork 0
Code Issues 1 Pull Requests 28 Packages Projects Releases Wiki Activity

feat: ensure kube-proxy gets phased out during 1.32 upgrade

Browse Source
This commit is contained in:
Stefan Reimer 2025-05-30 17:55:14 +00:00
parent 1538ea0d45
commit 49fa7b3c42
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
admin/hooks-1.32.sh
View File

@ -5,6 +5,9 @@ pre_control_plane_upgrade_cluster() {
if [ "$PLATFORM" != "gke" ];then
# patch multus DS to ONLY run pods on 1.31 controllers
kubectl patch ds kube-multus-ds -n kube-system -p '{"spec": {"template": {"spec": {"nodeSelector": {"node.kubernetes.io/kubezero.version": "v1.31.6"}}}}}' || true
# patch kube-proxy DS to ONLY run pods on 1.31 controllers
kubectl patch ds kube-proxy -n kube-system -p '{"spec": {"template": {"spec": {"nodeSelector": {"node.kubernetes.io/kubezero.version": "v1.31.6"}}}}}' || true
fi
}
@ -28,6 +31,10 @@ pre_cluster_upgrade_final() {
kubectl delete ds kube-multus-ds -n kube-system
kubectl delete NetworkAttachmentDefinition cilium
kubectl delete crd network-attachment-definitions.k8s.cni.cncf.io
# remove kube-proxy
kubectl -n kube-system delete ds kube-proxy
kubectl -n kube-system delete cm kube-proxy
fi
set -e