kubeadm: Move .NodeName and .CRISocket to a common sub-struct#64210
kubeadm: Move .NodeName and .CRISocket to a common sub-struct#64210k8s-github-robot merged 3 commits intokubernetes:masterfrom
Conversation
There was a problem hiding this comment.
Given that this is the Kubelet ExtraArgs it's not entirely clear from a developer UX.
For example:
NodeRegistrationOptions.ExtraArgs
vs.
KubeletRegistrationOptions.ExtraArgs or
NodeRegistrationOptions.KubeletExtraArgs.
There was a problem hiding this comment.
I'll change this after we've discussed the naming with @fabriziopandini in the SIG meeting
There was a problem hiding this comment.
Do you patch b/c dynamic kubelet config is not default?
There was a problem hiding this comment.
No this is used when e.g. setting the master label/taint, and generically modifying the Node object.
There was a problem hiding this comment.
If we are considering convergence towards cluster API, the corresponding object is named machineSpec.
WDYT? it is too early for starting to unify naming?
There was a problem hiding this comment.
i think we should stick with something custom like NodeRegistrationOptions for now, mostly because of the ExtraArgs field, assuming it's going to be replaced with a config map eventually (i.e. graduate out of using args?). at a later point we can start converging towards the MachineSpec.
2c.
There was a problem hiding this comment.
What about creating validateNodeRegistrationOptions ?
There was a problem hiding this comment.
PS. It seems that ValidateNodeConfiguration doesn't validate node name and crisocket... could you kindly fix it?
There was a problem hiding this comment.
This is WIP, thanks for keeping me honest fixing this as well
There was a problem hiding this comment.
What about adding a note that explain difference between extra args and KubeletConfiguration (machine specific vs cluster wide)
b66dfe3 to
8bcbc1e
Compare
|
As per slack discussion we move on with this PR as it is. Small bits will follow |
timothysc
left a comment
There was a problem hiding this comment.
/lgtm
Please open an issue to determine long term plan for translating <> machinespec.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini, luxas, timothysc The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
[MILESTONENOTIFIER] Milestone Pull Request: Up-to-date for process @fabriziopandini @luxas @timothysc Pull Request Labels
|
|
/retest Review the full test history for this PR. Silence the bot with an |
|
Automatic merge from submit-queue (batch tested with PRs 64322, 64210, 64458, 64232, 64370). If you want to cherry-pick this change to another branch, please follow the instructions here. |
What this PR does / why we need it:
Regroups some common fields for
kubeadm initandkubeadm joinonly used for the initial node registration.Lets the user specify ExtraArgs to the kubelet.
Now also runs the dynamic env file creation for
kubeadm join.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes kubernetes/kubeadm#847
Follows-up #63887
Related to kubernetes/kubeadm#822
Special notes for your reviewer: WIP, but please review so we can finalize the direction of the PR
Release note:
@kubernetes/sig-cluster-lifecycle-pr-reviews @liztio