-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
kubeadm: override node registration options from command line (follow-up) #71323
kubeadm: override node registration options from command line (follow-up) #71323
Conversation
'kubeadm init' silently ignores --node-name and --cri-socket command line options if --config option is specified. Implemented setting 'name' and 'criSocket' options from the command line even if --config command line option is used.
/cc @neolit123 |
@bart0sh: GitHub didn't allow me to request PR reviews from the following users: seh. Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
@bart0sh thanks a lot
will double check it locally with git am
just in case.
/lgtm
/priority critical-urgent
/kind bug
/assign @fabriziopandini @timothysc |
tested locally with our integration test and manually. 👍 |
Fantastic! Thank you so much, Ed and Lubomir. |
@bart0sh thanks! @neolit123 thanks for testing! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bart0sh, fabriziopandini The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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 need to mention I'm everything but happy about this (same for join) from a correctness and code health perspective, but being pragmatic it's a pretty useful feature, and we do appreciate your feedback on what should be improved in kubeadm. So as I'm letting this and the same for join merge, we simply make the general contract that flags should override config.
When this has merged, make sure you open a fresh issue for v1.14 that makes sure we track starting to merge flags with config generically and correctly in the next version.
/lgtm
I thought it's a common practice for command line utilities, no?
I'd be happy to work on that. Can you create an issue? |
No, only the kubelet does it correctly. Hence the proposal of https://docs.google.com/document/d/1nZnzJD9dC0xrtEla2Xa-J6zobbC9oltdHIJ3KKSSIhk/edit#.
See linked proposal for work items. I'll create an issue. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
It turned out after the discussion in the similar PR that 'kubeadm init' also suffers from this issue. This fix is almost identical to the previous one:
'kubeadm init' silently ignores --node-name and --cri-socket
command line options if --config option is specified.
Implemented setting 'name' and 'criSocket' options from the command
line even if --config command line option is used.
Does this PR introduce a user-facing change?: