-
Notifications
You must be signed in to change notification settings - Fork 39k
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: Make dry-run is configurable in initConfiguration and joinConfiguration #119279
Conversation
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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.
/approve
we should mention this and the join config addition in the v1beta4 doc.go |
yes, I fogot to include the change in the doc.go. Let's hold this until v1beta4 is enabled, so that I can add testcases for this. |
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
/hold
drop the hold when needed, please.
LGTM label has been added. Git tree hash: fb9dc78e5f3bf2bc7cb94018082918bb682be9d8
|
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.
actually...why not add the change in joinconfiguration too here? no need for separate PR. separate commit seems ok to me, but it's your preference.
The `dry-run` flag was able to use with the config file, since it was not configurable in the config file. Make it configurable in v1beta4, so that eventually, kubeadm could deprecate the flag and suggest to use the config file instead. Signed-off-by: Dave Chen <dave.chen@arm.com>
Signed-off-by: Dave Chen <dave.chen@arm.com>
Done |
/retitle kubeadm: Make dry-run is configurable in initConfiguration and joinConfiguration |
dry-run
is configurable in initConfiguration
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
/hold
thanks, if there are no other comments please drop the hold.
LGTM label has been added. Git tree hash: 28ff98927db69f227f0194947287e2d681163203
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chendave, neolit123 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 |
/unhold |
The
dry-run
flag was able to use with the config file, since it was not configurable in the config file.Make it configurable in v1beta4, so that eventually, kubeadm could deprecate the flag and suggest to use the config file instead.
/kind feature
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Part of: #kubernetes/kubeadm#2890
Part of: #kubernetes/kubeadm#2902
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/hold
After I finishing this, I realized this should wait until the v1beta4 is enabled across the code base, so we can
initData.cfg.DryRun
to be consistent withinitData.dryRun