Skip to content
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

"[bootstraptoken]" and "[bootstrap-token]" at kubeadm init #1357

Closed
atoato88 opened this issue Jan 23, 2019 · 4 comments · Fixed by kubernetes/kubernetes#73237
Closed

"[bootstraptoken]" and "[bootstrap-token]" at kubeadm init #1357

atoato88 opened this issue Jan 23, 2019 · 4 comments · Fixed by kubernetes/kubernetes#73237
Labels
area/UX kind/bug Categorizes issue or PR as related to a bug. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/backlog Higher priority than priority/awaiting-more-evidence.
Milestone

Comments

@atoato88
Copy link

Is this a BUG REPORT or FEATURE REQUEST?

BUG REPORT

Versions

kubeadm version (use kubeadm version):v1.13.2

Environment:

  • Kubernetes version (use kubectl version):v1.13.2
  • Cloud provider or hardware configuration:N/A
  • OS (e.g. from /etc/os-release):18.04.1 LTS (Bionic Beaver)
  • Kernel (e.g. uname -a):4.15.0-43-generic
  • Others:N/A

What happened?

When run kubeadm init, I got following output. (Command finished successfully.)

...
[mark-control-plane] Marking the node ubuntu-master01 as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
[bootstrap-token] Using token: tucvyo.5kmgswqycqewn09k
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[bootstraptoken] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstraptoken] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstraptoken] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstraptoken] creating the "cluster-info" ConfigMap in the "kube-public" namespace
[addons] Applied essential addon: CoreDNS
...

In this output, there are two strings for meaning of bootstrap token which are "bootstraptoken" and "bootstrap-token".

What you expected to happen?

It should be unified with same word.
There are 2 options to fix it.

  1. Change "[bootstrap-token]" to "[bootstraptoken]"
  2. Change "[bootstraptoken]" to "[bootstrap-token]"

At commit kubernetes/kubernetes@e743f0e, "bootstrap-token" is introduced. And there are "bootstraptoken" at other code.
IMHO, we should select option 1.

How to reproduce it (as minimally and precisely as possible)?

Just run kubeadm init.

Anything else we need to know?

If my opinion is ok( option 1 above ), I'll fix it.

@neolit123 neolit123 added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. area/UX good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence. labels Jan 23, 2019
@neolit123 neolit123 added this to the v1.14 milestone Jan 23, 2019
@neolit123 neolit123 removed good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jan 23, 2019
@neolit123
Copy link
Member

@atoato88 thanks for the report.
we should go with option 2 because we have other phases like [mark-control-plane] that use - to separate words.

let me know if you can send a PR?

@MalloZup
Copy link

thx @atoato88 for this catch 🚀

@atoato88
Copy link
Author

@neolit123 OK, I’ll fix it with option 2.

@neolit123
Copy link
Member

thanks!
/lifecycle active

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/UX kind/bug Categorizes issue or PR as related to a bug. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants