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.

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

maxUnavailable for StatefulSets #961

Open
4 of 8 tasks
krmayankk opened this issue Apr 14, 2019 · 139 comments
Open
4 of 8 tasks

maxUnavailable for StatefulSets #961

krmayankk opened this issue Apr 14, 2019 · 139 comments
Assignees
Labels
sig/apps Categorizes an issue or PR as relevant to SIG Apps. stage/beta Denotes an issue tracking an enhancement targeted for Beta status

Comments

@krmayankk
Copy link

krmayankk commented Apr 14, 2019

Enhancement Description

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

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Apr 14, 2019
@krmayankk
Copy link
Author

/sig auth

@k8s-ci-robot k8s-ci-robot added sig/auth Categorizes an issue or PR as relevant to SIG Auth. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 14, 2019
@krmayankk
Copy link
Author

/assign @krmayankk

@krmayankk
Copy link
Author

/milestone v1.15

@k8s-ci-robot k8s-ci-robot added this to the v1.15 milestone Apr 14, 2019
@kacole2
Copy link
Contributor

kacole2 commented Apr 14, 2019

/stage alpha

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Apr 14, 2019
@kacole2 kacole2 added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Apr 14, 2019
@mrbobbytables
Copy link
Member

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

@krmayankk
Copy link
Author

@mrbobbytables no this is specific to sig-apps

@mrbobbytables
Copy link
Member

@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

@k8s-ci-robot k8s-ci-robot added sig/apps Categorizes an issue or PR as relevant to SIG Apps. and removed sig/auth Categorizes an issue or PR as relevant to SIG Auth. labels Apr 18, 2019
@craiglpeters
Copy link
Contributor

@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
Copy link
Author

@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
Copy link
Contributor

@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 craiglpeters added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels May 1, 2019
@craiglpeters
Copy link
Contributor

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.15 milestone May 1, 2019
@craiglpeters craiglpeters added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels May 1, 2019
@craiglpeters
Copy link
Contributor

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

/milestone v1.15

@k8s-ci-robot k8s-ci-robot added this to the v1.15 milestone May 1, 2019
@draveness
Copy link
Contributor

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

@kacole2
Copy link
Contributor

kacole2 commented May 6, 2019

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
Copy link
Contributor

@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.

@ruheenaansari34
Copy link

ruheenaansari34 commented May 22, 2023

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
Copy link
Contributor

soltysh commented May 31, 2023

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

@Atharva-Shinde
Copy link
Contributor

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
Copy link
Contributor

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.28 milestone Jun 16, 2023
@AdminTurnedDevOps
Copy link

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
Copy link
Member

Rishit-dagli commented Jul 1, 2023

@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

@npolshakova npolshakova added this to the v1.29 milestone Sep 18, 2023
@sftim
Copy link
Contributor

sftim commented Sep 20, 2023

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

@npolshakova
Copy link

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
Copy link
Member

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!

@sreeram-venkitesh
Copy link
Member

Hi @krmayankk , checking in once more as we approach the 1.29 enhancement freeze deadline on 01:00 UTC Friday, 6th October 2023. The status of this enhancement is marked as at risk. It looks like #3997 will address most of the requirements. Let me know if I missed anything. Thanks!

@npolshakova
Copy link

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

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.29 milestone Oct 6, 2023
@salehsedghpour
Copy link
Contributor

/remove-label lead-opted-in

@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Jan 6, 2024
@atiratree
Copy link
Member

@kerthcet are you able to work on pushing this to beta in 1.30 timeframe?

@kerthcet
Copy link
Member

kerthcet commented Jan 30, 2024

Feel free to take this. Out of bandwidth.
/unassign

@knelasevero
Copy link

/assign
Taking over this one

@soltysh
Copy link
Contributor

soltysh commented Feb 5, 2024

/label lead-opted-in
/stage beta
/milestone v1.30

@k8s-ci-robot k8s-ci-robot added this to the v1.30 milestone Feb 5, 2024
@k8s-ci-robot k8s-ci-robot added the lead-opted-in Denotes that an issue has been opted in to a release label Feb 5, 2024
@meganwolf0
Copy link

Hello @krmayankk @kerthcet 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024.

This enhancement is targeting for stage beta for 1.30 (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: v1.30. 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, we would just need to update the following:

  • Updated KEP readme to latest template and provide information in missing sections: Release Signoff Checklist, Design Details, Test Plan subsections (unit, integration, e2e), Version Skew Strategy, Additional question in Scalability (Can enabling / using this feature result in resource exhaustion of some node resources (PIDs, sockets, inodes, etc.)?)
  • Update the kep.yaml for stage and latest-milestone
  • Update the PRR with beta

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!

@soltysh
Copy link
Contributor

soltysh commented Feb 7, 2024

@meganwolf0 just talked with @knelasevero we're not gonna be able to finish it off for 1.30, so I'm removing it from milestone

/remove-label lead-opted-in
/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.30 milestone Feb 7, 2024
@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Feb 7, 2024
@salehsedghpour
Copy link
Contributor

/milestone clear

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/apps Categorizes an issue or PR as relevant to SIG Apps. stage/beta Denotes an issue tracking an enhancement targeted for Beta status
Projects
Status: Removed from Milestone
Status: Removed from Milestone
Status: Removed from Milestone
Status: Backlog
Development

Successfully merging a pull request may close this issue.