Allow StatefulSet to control start replica ordinal numbering

[pwschuurman]

Enhancement Description

• One-line enhancement description (can be used as a release note): Added a feature that allows a StatefulSet to start numbering replicas from an arbitrary non-negative ordinal, using the .spec.ordinals.start field.
  • KEP-3335 Link
  • KEP-3335 PR: KEP-3335: StatefulSet Start Ordinal #3336
• Discussion Link:
  • sig-storage June 2, 2022
  • sig-apps June 13, 2022
  • sig-multicluster July 26, 2022
• Primary contact (assignee): @pwschuurman
• Responsible SIGs: sig-apps, sig-multicluster, sig-storage
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.26
  • Beta release target (x.y): 1.27
  • Stable release target (x.y): 1.31
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-3335: StatefulSet Start Ordinal #3336
  • Code (k/k) update PR(s): Add implementation of KEP-3335, StatefulSetSlice kubernetes#112744
  • Docs (k/website) update PR(s): Add initial documentation for StatefulSetSlice feature website#37224
• Beta
  • KEP (k/enhancements) update PR(s): KEP-3335: Update beta milestone to 1.27 #3768
  • Code (k/k) update PR(s): Move StatefulSetStartOrdinal feature gate to beta kubernetes#115260
  • Metrics (k/kube-state-metrics) update PR(s): Add StatefulSet Start Ordinal metrics for KEP-3335 kube-state-metrics#1959
  • Tests (k/k) unit PR(s): Add enablement/disablement unit test for StatefulSetStartOrdinal feature kubernetes#115536
  • Tests (k/k) integration PR(s): Add integration tests for StatefulSetStartOrdinal feature kubernetes#115466
  • Tests (k/k) e2e PR(s): Add e2e tests for StatefulSetStartOrdinal feature kubernetes#115468
  • Docs (k/website) update(s): Update StatefulSetStartOrdinal documentation to target beta in 1.27 website#39823
• Stable
  • KEP (k/enhancements) update PR(s): KEP-3335: Update stable milestone to 1.31 #4694
  • Code (k/k) update PR(s): Promote StatefulSetStartOrdinal to stable in 1.31 kubernetes#125374
  • Metrics (k/kube-state-metrics) update PR(s): feat: Promote kube_statefulset_ordinals_start from ALPHA -> STABLE kube-state-metrics#2415
  • Docs (k/website) update(s): Remove StatefulSetStartOrdinal feature gate to target stable in 1.31 website#46719
  • KEP (k/enhancements) status implemented PR(s): Update KEP-3335 kep.yaml to status: implemented #4955

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

[k8s-triage-robot]

The Kubernetes project currently lacks enough 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 stale
• Mark this issue or PR as rotten with /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 stale

[pwschuurman]

/sig multicluster

[JeremyOT]

/label lead-opted-in

[rhockenbury]

/milestone v1.26
/label tracked/yes
/stage alpha

[ruheenaansari34]

Hello @pwschuurman 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage alpha for 1.26 (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.26
• 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 just need to merge #3336, which will take care of above requirements.

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!

[ruheenaansari34]

Quick reminder - Enhancement freeze is 2 days away. If you are still looking to get this enhancement into v1.26, please plan to get the PR #3336 merged.

[pwschuurman]

Hi @ruheenaansari34, #3336 has been merged.

[pwschuurman]

/sig apps

[pwschuurman]

/remove-sig multicluster

[dipesh-rawat]

Hi @pwschuurman 👋, 1.31 Enhancements team here,

Just a quick friendly reminder as we approach the enhancements freeze later this week, at 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

The current status of this enhancement is marked as at risk for enhancement freeze. There are a few requirements mentioned in the comment #3335 (comment) that still need to be completed.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[soltysh]

@dipesh-rawat which bits exactly are missing, I've looked at the comment you've mentioned above and it looks like #4694 resolved them all, no?

[dipesh-rawat]

@soltysh I see the pull request #4694 was merged after the reminder comment was posted. With everything now merged, all the requirements are in place, and this enhancement looks good.

[dipesh-rawat]

Hello @pwschuurman 👋, 1.31 Enhancements team here.

Now that PR #4694 has been merged, all the KEP requirements are in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

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

[soltysh]

You're right I didn't notice that it merged in between 😉

[a-mccarthy]

Hi @pwschuurman, 👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines.

Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[a-mccarthy]

hello, @pwschuurman, friendly reminder about the upcoming blog opt-in and placeholder deadline on July 3rd. Please open a blog placeholder PR if you are interested in contributing a blog.

[dipesh-rawat]

Hey again @pwschuurman 👋, 1.31 Enhancements team here,

Just checking in as we approach code freeze at at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):

• Promote StatefulSetStartOrdinal to stable in 1.31 kubernetes#125374

Additionally, please let me know if there are any other PRs in k/k not listed in the description that we should track for this KEP, so that we can maintain accurate status.

If you anticipate missing code freeze, you can file an exception request in advance.

The status of this enhancement is marked as at risk for code freeze.

[dipesh-rawat]

Hey again @pwschuurman 👋, 1.31 Enhancements team here,

Just a quick friendly reminder as we approach code freeze in around two weeks time, at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

The current status of this enhancement is marked as at risk for code freeze. There are a few requirements mentioned in the comment #3335 (comment) that still need to be completed.

If you anticipate missing code freeze, you can file an exception request in advance.

[dipesh-rawat]

Hey again @pwschuurman 👋, 1.31 Enhancements team here,

Just a quick friendly reminder as we approach code freeze next week, at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

The current status of this enhancement is marked as at risk for code freeze. There are a few requirements mentioned in the comment #3335 (comment) that still need to be completed.

If you anticipate missing code freeze, you can file an exception request in advance.

[dipesh-rawat]

Hey again @pwschuurman 👋, 1.31 Enhancements team here,

Just a quick friendly reminder as we approach code freeze in less than 2 days, at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

The current status of this enhancement is marked as at risk for code freeze. There are a few requirements mentioned in the comment #3335 (comment) that still need to be completed.

If you anticipate missing code freeze, you can file an exception request in advance.

[sreeram-venkitesh]

Hi @pwschuurman @soltysh, with kubernetes/kubernetes#125374 merged, are we good to mark this KEP as tracked for code freeze?

[pwschuurman]

Hi @sreeram-venkitesh, yes, kubernetes/kubernetes#125374 is the only PR necessary to target 1.31.

[dipesh-rawat]

Hi @pwschuurman Thanks for confirmation.

Everything seems to be in place for this KEP issue now that the following code implementation PR have been merged.

• Promote StatefulSetStartOrdinal to stable in 1.31 kubernetes#125374

This enhancement is now marked as tracked for code freeze for the 1.31 Code Freeze!

[tjons]

@pwschuurman in preparation for the next release, could you kindly update the kep.yaml file for this KEP to status: implemented and then close this out?

[tjons]

Hello 👋 1.32 Enhancements Lead here,

I'm closing milestone 1.31 now,
If you have more work on this enhancement to complete in v1.32, please 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 and finally add /milestone v1.32. Thanks!

/milestone clear

[tjons]

Hi, enhancements lead here - I inadvertently added this to the 1.32 tracking board 😀. Please readd it if you wish to progress this enhancement in 1.32.

/remove-label lead-opted-in

[pwschuurman]

@pwschuurman in preparation for the next release, could you kindly update the kep.yaml file for this KEP to status: implemented and then close this out?

Yes, filed #4955