maxUnavailable for StatefulSets

[krmayankk]

Enhancement Description

• One-line enhancement description (can be used as a release note): Implement maxUnavailable for StatefulSets
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-apps/961-maxunavailable-for-statefulset/README.md
• Primary contact (assignee): @atiratree @knelasevero
• Responsible SIGs: sig-apps
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.24
  • Beta release target (x.y): TBD
  • Stable release target (x.y): TBD
• Alpha
  • KEP (k/enhancements) update PR(s): add initial KEP for maxUnavailable in StatefulSets #678 update proposal for maxUnavailable for statefulsets #1010 Add PRR information for maxUnavailable #2688 KEP: 961: Updating release info maxUnavailable for StatefulSet #2889 KEP-961: Update release information for maxUnavailable #3100
  • Code (k/k) update PR(s): API: maxUnavailable for StatefulSet kubernetes#82162
  • Docs (k/website) update PR(s): Document the MaxUnavailableStatefulSet feature website#32596
• Beta
  • KEP (k/enhancements) update PR(s):
    • KEP-961: Bump Statefulset maxUnavailable to beta #3997
    • KEP-961: Bump Statefulset maxUnavailable to beta (built on top of #3997) #4474
  • Code (k/k) update PR(s):
  • Docs (k/website) update(s):

Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement

[krmayankk]

/sig auth

[krmayankk]

/assign @krmayankk

[krmayankk]

/milestone v1.15

[kacole2]

/stage alpha

[mrbobbytables]

@krmayankk should this be sig auth? The KEP itself refers to sig-apps.

[krmayankk]

@mrbobbytables no this is specific to sig-apps

[mrbobbytables]

@krmayankk it has the responsible sig list as sig-auth 'in the post and is labeled with auth.

• Responsible SIGs: sig-auth

Would you mind updating the issue?

Thanks!

/remove-sig auth
/sig apps

[craiglpeters]

@krmayankk, Kubernetes 1.15 Enhancement Freeze is 4/30/2019. To be included in the Kubernetes 1.15 milestone, KEPs are required to be in an "Implementable" state with proper test plans and graduation criteria. Please submit any PRs needed to make this KEP adhere to inclusion criteria. If this will slip from the 1.15 milestone, please let us know so we can make appropriate tracking changes.

[krmayankk]

@craiglpeters here is the PR #1010 I will try to see if i can get some decision on this , in the next 1-2 days. If yes, i can try an exception for this enhancement to be implementable in 1.15. If no decision is nearing, will ask you to remove it from tracking.

[craiglpeters]

@krmayankk, Enhancement Freeze for Kubernetes 1.15 has passed and this did not meet the deadline. This is now being removed from the 1.15 milestone and the tracking sheet. If there is a need for this to be in 1.15, please file an Enhancement Exception. Thank you.

[craiglpeters]

/milestone clear

[craiglpeters]

@krmayankk please work to get the KEP to the implementable state quickly

/milestone v1.15

[draveness]

Is this enhancement will be included in milestone v1.15? I'd like to take this if it becomes implementable.

[kacole2]

This is still being tracked but I don't see an exception request submitted nor the KEP in an implementable state. @craiglpeters what's the status of this?

[craiglpeters]

@kacole2 an exception request was filed on May 1st. However this still is not in the implementable state, so I recommend moving out of 1.15 tracking.

[salehsedghpour]

/milestone clear

[k8s-triage-robot]

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

[atiratree]

/remove-lifecycle stale

[atiratree]

@knelasevero what is the status of graduating this to beta? Can you please summarize all the issue that have to be fixed?

[knelasevero]

kubernetes/kubernetes#112307 is a blocker for graduation.

But even before that minReadySecond specific issues need to be solved, issues like:
kubernetes/kubernetes#108266
kubernetes/kubernetes#119352
kubernetes/kubernetes#123918
kubernetes/kubernetes#119234

Besides that, consensus did not seem to be reached with regard to metrics :( #4474 (comment)

Betting on this fix for some of those issues, but not all of them: kubernetes/kubernetes#123975 and tests taking most time.

Help appreciated with some of those issues

[knelasevero]

@leomichalski @bersalazar @navarrovmn

[sreeram-venkitesh]

@knelasevero Are you planning to graduate this KEP to beta in the v1.31 release?

[k8s-triage-robot]

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-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[atiratree]

/remove-lifecycle rotten

[k8s-triage-robot]

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

[pochtmeister]

/remove-lifecycle rotten

[kerthcet]

Seems still in alpha now @atiratree @knelasevero do you know the process right now? Thanks.

[gjkim42]

/remove-lifecycle rotten

I think we need some input here as this feature has been in the alpha stage since v1.24.

[gjkim42]

/remove-lifecycle stale

[ahg-g]

@msau42 are there plans to graduate this?

[soltysh]

This was primarily driven by sig-apps, but currently we don't have anyone interested in pushing this forward. So sadly not in plans for 1.33. The biggest blocker to move this feature forward was lacking metric in statefulset controller, which we could try to work on in 1.33 and eventually consider beta graduation in 1.34. But that's a lot of ifs, and having an interested party driving this forward will be of great help.