Skip to content
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.

Sign up for GitHub

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

Jump to bottom

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

Open
3 tasks done
kerthcet opened this issue Apr 9, 2024 · 4 comments
Open
3 tasks done

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

kerthcet opened this issue Apr 9, 2024 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@kerthcet
Copy link
Contributor

kerthcet commented Apr 9, 2024 •
edited
Loading

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.
@kerthcet kerthcet added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 9, 2024
@k8s-ci-robot k8s-ci-robot added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Apr 9, 2024
@kannon92
Copy link
Contributor

Are you asking for a CLI to handle roll outs? Or should we explore kubectl rollout with lws?

@kerthcet
Copy link
Contributor Author

I guess it's not possible to support custom resources with kubectl rollout? https://kubernetes.io/docs/reference/kubectl/generated/kubectl_rollout/#synopsis

If we can, wonderful!

@kerthcet kerthcet mentioned this issue Apr 11, 2024
Closed
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 10, 2024
@kerthcet
Copy link
Contributor Author

kerthcet commented Aug 5, 2024

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kannon92 @kerthcet @k8s-ci-robot @k8s-triage-robot