Add minReadySeconds to Statefulsets

[ravisantoshgudimetla]

Enhancement Description

• One-line enhancement description (can be used as a release note): Add minReadySeconds to Statefulsets

• Kubernetes Enhancement Proposal:

• Discussion Link: Support MinReadySeconds on StatefulSet kubernetes#65098

• Primary contact (assignee): @ravisantoshgudimetla

• Responsible SIGs: sig-apps

• Enhancement target (which target equals to which milestone):

  • Alpha release target (x.y): 1.22
  • Beta release target (x.y): 1.23
  • Stable release target (x.y): 1.25

• Alpha

  • KEP (k/enhancements) update PR(s): Introduce minReadySeconds in StatefulSets #2607
  • Code (k/k) update PR(s): api: Add min ready seconds & availablereplicas for statefulsets kubernetes#100842
  • Docs (k/website) update PR(s): Add docs for minReadySeconds in StatefulSet website#27683

• Beta

  • KEP (k/enhancements) update PR(s): Promote STS minReadySeconds to beta #2824
  • Code (k/k) update PR(s): Promote min ready sec sts beta kubernetes#104045
  • Docs (k/website) update(s): [docs]: Promote STS minReadySeconds to beta website#30435

• Stable

  • KEP (k/enhancements) update PR(s): KEP-2599: Promote STS minReadySeconds to GA #3354
  • Code (k/k) update PR(s): Promote minReadySeconds to GA kubernetes#110896
  • Docs (k/website) update(s): Promote StatefulSet MinReadySeconds to GA website#35539

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

[ravisantoshgudimetla]

/sig apps

[soltysh]

/assign @ravisantoshgudimetla

[soltysh]

/milestone v1.22

[soltysh]

/stage alpha

[JamesLaverack]

👋 v1.22 Enhancements Lead here. This looks all set for enhancements freeze so I've set it as "Tracked" for this release on the tracking sheet.

[JamesLaverack]

Hey @ravisantoshgudimetla, can you confirm if kubernetes/kubernetes#100842
and kubernetes/kubernetes#101316 are the only k/k PRs required for this enhancement in v1.22?

[ravisantoshgudimetla]

Hi @JamesLaverack, this is the docs kubernetes/website#27683 remaining

[salaxander]

/milestone v1.23

[jlbutler]

Hi @ravisantoshgudimetla 👋 1.23 Docs lead here.

This enhancement is marked as 'Needs Docs' for the 1.23 release.

Please follow the steps detailed in the documentation to open a PR against the dev-1.23 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu November 18, 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]

Hi @ravisantoshgudimetla, 1.23 Enhancements Shadow here 👋

Looks like this enhancement's code PR kubernetes/kubernetes#104045 has been merged and is ready for Code Freeze on November 16th

[chrisnegus]

Hi @ravisantoshgudimetla, 1.23 docs shadow here. I noticed that this feature was documented in a blog for 1.22. If you think this requires documentation in the official docs, please open a PR as @jlbutler described above. Also, let me know if you would like help writing the content.

[ravisantoshgudimetla]

I'll open a docs PR this week.

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[soltysh]

/milestone v1.25
/stage stable

[marosset]

Hello @ravisantoshgudimetla 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 16, 2022.

For note, This enhancement is targeting for stage stable for 1.25 (correct me, if otherwise)

Here's where this enhancement currently stands:

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

Looks like for this one, we would just need to update the following:

• Add updated detailed Test Plan section to this KEP
• Complete and merge an production readiness review targeting stable release

It looks like #3354 will address these requirements.

For note, 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!

[marosset]

Hello @ravisantoshgudimetla 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 23, 2022.

For note, This enhancement is targeting for stage stable for 1.25 (correct me, if otherwise)

Here’s where this enhancement currently stands:

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

With all the KEP requirements in place & merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

For note, the status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[kcmartin]

Hello @ravisantoshgudimetla 👋, 1.25 Release Docs Lead here.
This enhancement is marked as ‘Needs Docs’ for 1.25 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.25 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by August 4.
 Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

[jasonbraganza]

Hi @ravisantoshgudimetla 👋

Checking in once more as we approach 1.25 code freeze at 01:00 UTC on Wednesday, 3rd August 2022.

Please ensure the following items are completed:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are fully merged by the code freeze deadline.

I was not able to find any k/k PRs corresponding to this KEP. Could you please point them here, if there are any?
Or if you are planning to raise k/k PRs, please link them here in the issue.

The status of this enhancement is currently marked as At Risk

Thank you.

[atiratree]

opened the docs update kubernetes/website#35539

[jasonbraganza]

Hello @ravisantoshgudimetla 👋

Just a gentle reminder from the enhancement team as we approach 1.25 code freeze at 01:00 UTC on Wednesday, 3rd August 2022. (less than a week to go)

Can you confirm if this enhancement needs any k/k PRs? If so, please link them here in the issue.
The status of this enhancement is currently marked as at risk

Thank you.

[jasonbraganza]

Hello @ravisantoshgudimetla 👋

Found this PR kubernetes/kubernetes#110896, that promotes this enhancement to GA.
It is merged as well, so marking the status of this enhancement as tracked.

Thank you.

[soltysh]

@jasonbraganza updated the description to have all the correct links in a single place 😅

[jasonbraganza]

oh hurrah! thank you :)

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

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

This bot triages issues and PRs 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 or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

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.