![]() Automatic merge from submit-queue New command: "kubeadm token generate" As part of #33930, this PR adds a new top-level command to kubeadm to just generate a token for use with the init/join commands. Otherwise, users are left to either figure out how to generate a token on their own, or let `kubeadm init` generate a token, capture and parse the output, and then use that token for `kubeadm join`. At this point, I was hoping for feedback on the CLI experience, and then I can add tests. I spoke with @mikedanese and he didn't like the original propose of `kubeadm util generate-token`, so here are the runners up: ``` $ kubeadm generate-token # <--- current implementation $ kubeadm generate token # in case kubeadm might generate other things in the future? $ kubeadm init --generate-token # possibly as a subcommand of an existing one ``` Currently, the output is simply the token on one line without any padding/formatting: ``` $ kubeadm generate-token 1087fd.722b60cdd39b1a5f ``` CC: @kubernetes/sig-cluster-lifecycle **Release note**: <!-- Steps to write your release note: 1. Use the release-note-* labels to set the release note state (if you have access) 2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. --> ``` release-note New kubeadm command: generate-token ``` |
||
---|---|---|
.. | ||
helpers | ||
build.sh | ||
cross.sh | ||
test-cmd.sh | ||
test-e2e-node.sh | ||
test-integration.sh | ||
test-kubeadm-cmd.sh | ||
test.sh | ||
verify.sh | ||
vet.sh |