-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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: Allow mixing Init and Join Configurations #69426
Conversation
Thanks for this fix! |
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.
@rosti Thank you for doing this!
/approve
minor comments, once you address LGTM
Also, we need to try and get this cherry-picked today!
} | ||
} | ||
if mutuallyExclusiveCount > 1 { | ||
glog.Warningf("WARNING: configuration kinds %v are mutually exclusive", mutuallyExclusive) |
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 wouldn't say mutually exclusive here, b/c if it were there would be an error.
Maybe
"Detected resource kinds that may not apply: %v"
{ | ||
name: "MustNotMixInitJoin", | ||
name: "CanMixInitJoin", |
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.
Could you put a comment above this test.
To the casual reader this would be confusing.
ef05120
to
d5460b5
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.
/lgtm
/approve
/retest Review the full test history for this PR. Silence the bot with an |
1 similar comment
/retest Review the full test history for this PR. Silence the bot with an |
This change allows mixing InitConfiguration/ClusterConfiguration with JoinConfiguration in a single YAML file, by performing the following changes: - Replace the explicit error in `DetectUnsupportedVersion` with a warning. - Modify `NodeConfigFileAndDefaultsToInternalConfig` to use only `JoinConfiguration`. Signed-off-by: Rostislav M. Georgiev <rostislavg@vmware.com>
d5460b5
to
f0d82fb
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini, rosti, timothysc 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 |
Thanks for the quick reaction @fabriziopandini ! |
/retest Review the full test history for this PR. Silence the bot with an |
/test pull-kubernetes-e2e-gce |
…upstream-release-1.12 Automated cherry pick of #69426: kubeadm: Allow mixing Init and Join Configurations
What this PR does / why we need it:
This change allows mixing InitConfiguration/ClusterConfiguration with
JoinConfiguration in a single YAML file, by performing the following changes:
DetectUnsupportedVersion
with a warning.NodeConfigFileAndDefaultsToInternalConfig
to use onlyJoinConfiguration
.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Refs kubernetes/kubeadm#1152 (This is the short-term 1.12 solution to unblock the community).
Special notes for your reviewer:
/cc @kubernetes/sig-cluster-lifecycle-pr-reviews
/area kubeadm
/kind bug
/assign @fabriziopandini
/assign @timothysc
/cc @neolit123
Release note: