Closed Amulyam24 closed 4 months ago
/kind bug /area provider/ibmcloud
What steps did you take and what happened: With the current plan to move to k8s version 1.29 for PowerVS CI, testing showed thatkubeadm init fails on the control plane node. The issue is with kube-vip failing with 1.29 with the following:
kubeadm init
hostAliases do not work as static pod manifests in Kubernetes v1.29 #692
kube-vip requires super-admin.conf with Kubernetes 1.29 #684
What did you expect to happen: Cluster to be created successfully with k8s v1.29
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
/etc/os-release
/assign
/kind bug /area provider/ibmcloud
What steps did you take and what happened: With the current plan to move to k8s version 1.29 for PowerVS CI, testing showed that
kubeadm init
fails on the control plane node. The issue is with kube-vip failing with 1.29 with the following:hostAliases do not work as static pod manifests in Kubernetes v1.29 #692
kube-vip requires super-admin.conf with Kubernetes 1.29 #684
What did you expect to happen: Cluster to be created successfully with k8s v1.29
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):