enhancements: maxUnavailable for StatefulSets
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): TBD
- Stable release target (x.y): TBD
- Alpha
- KEP (
k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/678 https://github.com/kubernetes/enhancements/pull/1010 https://github.com/kubernetes/enhancements/pull/2688 https://github.com/kubernetes/enhancements/pull/2889 https://github.com/kubernetes/enhancements/pull/3100 - Code (
k/k) update PR(s): https://github.com/kubernetes/kubernetes/pull/82162 - Docs (
k/website) update PR(s): https://github.com/kubernetes/website/pull/32596
- KEP (
- Beta
- KEP (
k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/3997 - Code (
k/k) update PR(s): - Docs (
k/website) update(s):
- KEP (
Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement
About this issue
- Original URL
- State: open
- Created 5 years ago
- Comments: 131 (70 by maintainers)
I can help with this if you’re out of bandwidth @krmayankk
All good for 1.24 Code Freeze 🥳
This is important issue, would be great to see it in beta.
/reopen /remove-lifecycle rotten
@krmayankk Thanks. It’s working fine. kube-controller and kube-api is must enabled ‘–feature-gates=MaxUnavailableStatefulSet=true’ at the same time.
Hi @krmayankk 👋🏻 1.24 Docs shadow here.
This enhancement is marked as ‘Needs Docs’ for the 1.24 release.
Please follow the steps detailed in the documentation to open a PR against the dev-1.24 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu March 31, 11:59 PM PDT.
Also, if needed take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.
Thanks!
@gracenng this was updated in https://github.com/kubernetes/enhancements/pull/3100
thanks @supriya-premkumar for the reminder, the PR is very close, hoping to get it merged tomorrow. @kow3ns @janetkuo @ravisantoshgudimetla @alculquicondor https://github.com/kubernetes/kubernetes/pull/82162 any help is appreciated in moving this forward
https://github.com/kubernetes/enhancements/pull/2688 @JamesLaverack
Hi @krmayankk, 1.21 Enhancements Lead here. With Enhancements freeze in effect, we are not able to mark this as tracked without an exception. That being said, I did see that you filed an exception for this enhancement.
Once accepted, I can label this enhancement as tracked and start tracking it in the enhancements tracking sheet.
@kikisdeliveryservice yes please mark it for 1.20, i will start the kep update with readiness review section . implementation PR is here https://github.com/kubernetes/kubernetes/pull/82162 FYI @kow3ns @lavalamp
looks like @lavalamp is the API reviewer. the sig leads own milestone planning for component work
@savitharaghunathan no docs for alpha
@helayoty this will move to alpha in 1.18. API PR is here https://github.com/kubernetes/kubernetes/pull/82162
@kcmartin yes this will be marked alpha in 1.17 . there is active PR here https://github.com/kubernetes/kubernetes/pull/82162
@daminisatya we do not not require any docs for this feature since this is an alpha feature. So we are good.
Also I do realize, that you and are also from Salesforce 😃
@krmayankk it has the responsible sig list as
sig-auth'in the post and is labeled with auth.Would you mind updating the issue?
Thanks!
/remove-sig auth /sig apps