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
Remove deprecated kubectl --dry-run values. #105327
Remove deprecated kubectl --dry-run values. #105327
Conversation
@julianvmodesto: 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. |
/sig cli |
f96f006
to
d648744
Compare
The boolean values for --dry-run have been deprecated for removal since 1.18, more than 2 releases. The default value for --dry-run with the flag set and unspecified has been deprecated for removal since 1.18, more than 2 releases. Both values are now removed in this change. Any kubectl --dry-run usage no longer accepts --dry-run=(true|false) boolean values and usage now requires that a value of (client|server|none) is specified.
d648744
to
e0b7a85
Compare
/assign @KnVerey |
I'll also take a look at k8s.io docs, but I think everything ideally says --dry-run=client (at least) everywhere. |
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
Thanks!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: apelisse, julianvmodesto 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 |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
For 1.23, we removed the kubectl `--dry-run` empty default value (`--dry-run`) and boolean values (`--dry-run=true` and `--dry-run=false`). This change required requiring users to specify `--dry-run=client` or `--dry-run=server` due to a deprecation. This change was made in kubernetes#105327. After reconsideration, this change is not worth the churn for users. It's likely that many users rely on these values for automated and manual use cases. This change reverts kubernetes#105327 and re-introduces the values `--dry-run`, `--dry-run=true`, and `--dry-run=false`.
For 1.23, we removed the kubectl `--dry-run` empty default value (`--dry-run`) and boolean values (`--dry-run=true` and `--dry-run=false`). This change required requiring users to specify `--dry-run=client` or `--dry-run=server` due to a deprecation. This change was made in kubernetes#105327. After reconsideration, this change is not worth the churn for users. It's likely that many users rely on these values for automated and manual use cases. This change reverts kubernetes#105327 and re-introduces the values `--dry-run`, `--dry-run=true`, and `--dry-run=false`.
What type of PR is this?
/kind cleanup
/kind deprecation
What this PR does / why we need it:
The boolean values for --dry-run have been deprecated for removal since
1.18, more than 2 releases.
The default value for --dry-run with the flag set and unspecified has
been deprecated for removal since 1.18, more than 2 releases.
Both values are now removed in this change. Any kubectl --dry-run
usage no longer accepts --dry-run=(true|false) boolean values and usage
now requires that a value of (client|server|none) is specified.
Which issue(s) this PR fixes:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: