Force control plane node to be registered in k8s in standalone case #41
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
K0s control plane nodes are not listed in kubectl by default: https://docs.k0sproject.io/v1.28.4+k0s.0/FAQ/#why-doesnt-kubectl-get-nodes-list-the-k0s-controllers
K0s node is registered with `node-role.kubernetes.io/control-plane: true` label.
eromanova
force-pushed
the
templates-fixes
branch
from
1aebc4b to
1c8373c
Compare
eromanova
changed the title
Kshatrix
approved these changes
Jun 20, 2024
bnallapeta
pushed a commit
to bnallapeta/hmc
that referenced
this pull request
Nov 15, 2024
Force control plane node to be registered in k8s in standalone case
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
K0s control plane nodes are not listed in kubectl by default:
https://docs.k0sproject.io/v1.28.4+k0s.0/FAQ/#why-doesnt-kubectl-get-nodes-list-the-k0s-controllers