Skip to content

Support rolling out to specific versions akin to kubectl rollout #89

Open
@kerthcet

Description

What would you like to be added:

This is a regular need for workloads, we can see similar capacity with deployment, statefulset, daemonset, it generally looks like:
lws rollout xxx.

See https://kubernetes.io/docs/reference/kubectl/generated/kubectl_rollout/

Why is this needed:

When rolling update failed, we can rollback or rollout to specific versions.

Completion requirements:

/priority important-longterm

This enhancement requires the following artifacts:

  • Design doc
  • API change
  • Docs update

The artifacts should be linked in subsequent comments.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions