Support rolling back Deployments to previous revisions

[timoreimann]

Environment

Dashboard version: 1.8.0
Kubernetes version: v1.8.7-gke.1
Operating system: 
Node.js version:
Go version:

Steps to reproduce

Try to roll back a Deployment to a previous revision (i.e., what kubectl rollout undo does).

Observed result

No such UI interaction is available.

Expected result

A UI element is available that allows me to select from a list of recent revisions and roll back to any of them.

Motivation

Rolling back to a previous release is a fairly important operation as it allows to remedy critical situations quickly. While the functionality is accessible in kubectl as well, I find an integration into the Dashboard very desirable given that it's easier to use, especially for users that are not that familiar with kubectl.

Comments

I asked for the availability of this feature some time ago on Slack and got the response that it's worthwhile creating an issue. So I'm doing this now. :-)

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[timoreimann]

This issue still seems pretty relevant -- unstaling.

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[maciaszczykm]

/lifecycle frozen

[shu-mutou]

Ref: #4542

[huweihuang]

Is the rolling back function currently supported on the dashboard page？

[shu-mutou]

No, it's not supported yet.

[shu-mutou]

This is a function that kubectl implements by adding its own annotations, and it is necessary to maintain data structures that are not directly supported by the K8s API. In Dashboard, we are considering how to handle data that extends the K8s API, and the implementation has stopped.