Add feature to install kubernetes worker nodes #1183
Draft
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
|
Based on question in: |
AkihiroSuda
reviewed
Nov 20, 2022
|
Choosing the apiserver address and the flannel interface, with k3s and k8s: k3s: k8s: When having nodes with multiple interfaces, and Should deploy a DNS server, to be able to configure addresses (based on the MAC) |
afbjorklund
force-pushed
the
worker
branch
2 times, most recently
from
f82f520
to
a1bf0cc
Compare
If your instances are connected through a proper network, then it is possible to join additional workers to the control plane. Beyond the URL of the apiserver (running on port 6443), you will also need the secret "token" emitted by the initial installation. Signed-off-by: Anders F Björklund <[email protected]>
Signed-off-by: Anders F Björklund <[email protected]>
Signed-off-by: Anders F Björklund <[email protected]>
Signed-off-by: Anders F Björklund <[email protected]>
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.
If your instances are connected through a proper network,
then it is possible to join additional workers to the control plane.
Beyond the URL of the apiserver (running on port 6443),
you will also need the secret "token" emitted by the initial installation.
The two (or more) Kubernetes nodes will need to be able reach eachother, though.
The default network ("user") will not allow this, but it is possible to use "socket":
Probably still need the original NAT network to pull images, so needs eth0/eth1 ?
This is the setup done in minikube, originally by using the VirtualBox networks...