Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix kubeconfig issue with kube-vip: #206

Merged
merged 1 commit into from
Jan 23, 2025

Conversation

jacobweinstock
Copy link
Member

Description

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

Fixes: #

How Has This Been Tested?

How are existing users impacted? What migration steps/scripts do we need?

Checklist:

I have:

  • updated the documentation and/or roadmap (if required)
  • added unit or e2e tests
  • provided instructions on how to upgrade

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.

Signed-off-by: Jacob Weinstock <[email protected]>
@jacobweinstock jacobweinstock merged commit 532c02a into tinkerbell:main Jan 23, 2025
3 checks passed
@jacobweinstock jacobweinstock deleted the another-kubevip-fix branch January 23, 2025 18:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant