-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Add kubeadm
style bootstrap token secret support
#6663
Conversation
kubeadm
style bootstrap token secret support
1f2d40d
to
7db8022
Compare
Outstanding issues:
Auth debug logs
|
38c51d8
to
ca92ad7
Compare
With latest changes node auth is blocked when the node doesn't exist - but the messages leave something to be desired. On the server the log just says On the agent it says EDIT: This has been addressed. |
99868f6
to
8a84320
Compare
This is really really awesome. Thanks! Looking forward to this. |
8a84320
to
aee6d86
Compare
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.
I have reviewed the new commands and CLI and it looks good, I am waiting for #6615 to be merged and for this PR to be rebased before formal approval.
Will rebase once the CA rotation PR is merged |
Signed-off-by: Brad Davidson <[email protected]>
Allow bootstrapping with kubeadm bootstrap token strings or existing Kubelet certs. This allows agents to join the cluster using kubeadm bootstrap tokens, as created with the `k3s token create` command. When the token expires or is deleted, agents can successfully restart by authenticating with their kubelet certificate via node authentication. If the token is gone and the node is deleted from the cluster, node auth will fail and they will be prevented from rejoining the cluster until provided with a valid token. Servers still must be bootstrapped with the static cluster token, as they will need to know it to decrypt the bootstrap data. Signed-off-by: Brad Davidson <[email protected]>
Signed-off-by: Brad Davidson <[email protected]>
Signed-off-by: Brad Davidson <[email protected]>
aee6d86
to
06cb1b4
Compare
Signed-off-by: Brad Davidson <[email protected]>
06cb1b4
to
745c393
Compare
Proposed Changes
k3s token create
- same functionality askubeadm token create
Can be used to create time-limited join tokens that are automatically cleaned up by the controller-manager when the TTL expires. Tokens are for joining agents only. Servers must know the legacy join/encryption token.
Types of Changes
enhancement
Verification
k3s token create
to create a join tokenk3s token list
to list the tokenk3s token delete
to delete the tokenk3s token create --ttl 5m
to create a time-limited tokenTesting
Covered by CI
Linked Issues
User-Facing Change
Further Comments