You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge pull request #206 from jacobweinstock/another-kubevip-fix
Fix kubeconfig issue with kube-vip:
## Description
<!--- Please describe what this PR is going to change -->
Only the first control plane node needs to use the `super-admin.conf`. All other nodes need to use `admin.conf`. The file: `/run/kubeadm/kubeadm.yaml` is used to determine the first control plane node. This file is used by `kubeadm init` and `kubeadm init` is only run on the first control plane node.
## Why is this needed
<!--- Link to issue you have raised -->
Fixes: #
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
## How are existing users impacted? What migration steps/scripts do we need?
<!--- Fixes a bug, unblocks installation, removes a component of the stack etc -->
<!--- Requires a DB migration script, etc. -->
## Checklist:
I have:
- [ ] updated the documentation and/or roadmap (if required)
- [ ] added unit or e2e tests
- [ ] provided instructions on how to upgrade
0 commit comments