Support rolling out to specific versions akin to `kubectl rollout` - Githubissues

kubernetes-sigs / lws

LeaderWorkerSet: An API for deploying a group of pods as a unit of replication

Apache License 2.0

136 stars 26 forks source link

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

Open kerthcet opened 7 months ago

kerthcet commented 7 months ago

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:

[x] Design doc
[x] API change
[x] Docs update

The artifacts should be linked in subsequent comments.

kannon92 commented 7 months ago

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

kerthcet commented 7 months ago

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!

k8s-triage-robot commented 4 months ago

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

kerthcet commented 3 months ago

/lifecycle frozen