Closed Amulyam24 closed 4 months ago
Name | Link |
---|---|
Latest commit | 4dd2ee8937810c4b29fde0bf6d57eab65e178f77 |
Latest deploy log | https://app.netlify.com/sites/kubernetes-sigs-cluster-api-ibmcloud/deploys/66503caaaf4f570008a27224 |
Deploy Preview | https://deploy-preview-1798--kubernetes-sigs-cluster-api-ibmcloud.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
/lgtm awaiting approval of @mkumatag
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Amulyam24, mkumatag
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@mkumatag, should we back port this to release-0.8 branch?
@mkumatag, should we back port this to release-0.8 branch?
I feel not required, we aren't testing that branch aggressively!
What this PR does / why we need it: kube-vip has issues when being used with k8s 1.29. This PR fixes them by
kubeadm
to provision a separate Kubeconfig file calledsuper-admin.conf
and reducing theadmin.conf
User's access to the permissions provided by the cluster-admin ClusterRole. It is to be noted that in a multi-cluster setup, thesuper-admin.conf
is only created on the primary control plane node, which runskubeadm init
is failing because kube-vip deployment is hardcoded to useadmin.conf
but kube-vip requires elevated permissions to access the API server during cluster initialization, which are available only when using thesuper-admin.conf
.hostAliases
do not work as expected. Add a work around to mount the volumes to thekube-vip
pod manifest.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged): Fixes #1792Special notes for your reviewer:
/area provider/ibmcloud
Release note: