-
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
Switch kubectl rollout to directly rolling back deployments #70039
Conversation
/assign @janetkuo |
c7aebb9
to
0953948
Compare
0953948
to
02e92bf
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt 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 |
Another user visible change is that rollback no longer emits events. Worth mentioning in the release note. |
02e92bf
to
e266449
Compare
comments addressed |
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, I'll let Janet have final saying
/cc @tnozicka
e266449
to
57df11b
Compare
updated |
/lgtm Thanks! |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Removes kubectl use of the extensions/v1beta1 rollback API, which is deprecated and removed in apps/v1. This is a prereq of switching to apps/v1 completely and stopping serving the extensions/v1beta1 API.
Also correctly returns error codes when trying to rollback a deployment to a non-existent revision
xref #43214
Does this PR introduce a user-facing change?: