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): @krmayankk @kerthcet
• Responsible SIGs: sig-apps
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.24
  • Beta release target (x.y): 1.28
  • 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
  • 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.

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[yanrez]

This is important issue, would be great to see it in beta.

/reopen
/remove-lifecycle rotten

[k8s-ci-robot]

@yanrez: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

This is important issue, would be great to see it in beta.

/reopen
/remove-lifecycle rotten

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[kerthcet]

I can help with this if you're out of bandwidth @krmayankk

[yanrez]

This would be awesome in my opinion!

[ppbits]

I would like to help take this enhancement to Beta.

[helayoty]

/reopen
/remove-lifecycle rotten

[k8s-ci-robot]

@helayoty: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[kerthcet]

/assign

[soltysh]

/milestone v1.28
/label lead-opted-in

[krmayankk]

@kerthcet please go ahead. Thanks for helping out with this one. Feel free to ping me for reviews.

[ruheenaansari34]

Hello @krmayankk @kerthcet 👋, 1.28 Enhancements team here.

Just checking in as we approach enhancements freeze on 1:00 UTC on Friday 16th June 2023.

This enhancement is targeting for stage beta for 1.28 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.28
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would need to take care of all the above criteria including:

• Updated KEP readme using the latest template, especially Design Details, Test Plan, Graduation Criteria etc.
• Updated milestone and latest-milestone in kep.yaml
• Updated and merged PRR.

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[soltysh]

#3997 is the PR that should promote the feature to beta

[Atharva-Shinde]

Hello 👋, 1.28 Enhancements Lead here.
Unfortunately, this enhancement did not meet requirements for v1.28 enhancements freeze.
Feel free to file an exception to add this back to the release tracking process. Thanks!

[Atharva-Shinde]

/milestone clear

[AdminTurnedDevOps]

HI @krmayankk

1.28 Docs Shadow here.

Does this enhancement work planned for 1.28 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.28 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 20th July 2023.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[Rishit-dagli]

@AdminTurnedDevOps This is removed from 1.28 release so I have marked this as "removed form release" and there is no need for 1.28 docs PR

[sftim]

It's not too early to make a start on the v1.29 docs changes.

[npolshakova]

Hello @krmayankk, 1.29 Enhancements team here! Is this enhancement targeting 1.29? If it is, can you follow the instructions here to opt in the enhancement and make sure the lead-opted-in label is set so it can get added to the tracking board? Thanks!

[sreeram-venkitesh]

Hello @krmayankk 👋, v1.29 Enhancements team here.

Just checking in as we approach enhancements freeze on 01:00 UTC, Friday, 6th October, 2023.

This enhancement is targeting for stage beta for 1.29 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.29. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

For this KEP, all the above tasks would be completed with #3997. Adding on to @npolshakova's message above, if you're planning to include this KEP in the 1.29 release, please update the latest milestone to v1.29 and the beta milestone to 1.29 in the PR.

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!