-
Notifications
You must be signed in to change notification settings - Fork 797
Add url and token params for kubernetes templates #4505
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
Conversation
5c6f7dc to
14697a8
Compare
Allows joining an agent / worker to an existing cluster, instead of creating a control plane node and doing reset. Don't check for control plane config / images / processes, and don't output any message about the kubeconfig either. Signed-off-by: Anders F Björklund <[email protected]>
There was no error, but the Param was always empty map. Which made it impossible to customize the message text. Signed-off-by: Anders F Björklund <[email protected]>
42cc3b3 to
ac1bfb8
Compare
|
There should probably be some more "elegant" method, of propagating parameters from master to minions... Currrently you are required to run low-level commands on the node, and then copy them into a complex |
website/content/en/docs/examples/containers/kubernetes/_index.md
Outdated
Show resolved
Hide resolved
This reverts commit 93055a1. Signed-off-by: Anders F Björklund <[email protected]>
All commands are copied from the templates. This leads to some duplication, but so be it. Signed-off-by: Anders F Björklund <[email protected]>
ac1bfb8 to
6ad4fd4
Compare
| ```bash | ||
| limactl start --name k3s-0 --network lima:user-v2 template:k3s | ||
| printf "https://lima-%s.internal:6443\n" k3s-0 | ||
| # (The url for the start command printed here) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This printf does not seem needed?
Just set .param.url to https://lima-k3s-0.internal:6443 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is only needed when you change k3s-0, like in the test - but it was a workaround for the missing address
i.e. the k3s node creation doesn't record the endpoint IP anywhere, so I resorted to constructing it myself
AkihiroSuda
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
Allows joining an agent / worker to an existing cluster,
instead of creating a control plane node and doing reset.
Don't check for control plane config / images / processes,
and don't output any message about the kubeconfig either.
Fixes #4481