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

Allow StatefulSet to control start replica ordinal numbering #3335

Open
3 of 4 tasks
pwschuurman opened this issue Jun 3, 2022 · 24 comments
Open
3 of 4 tasks

Allow StatefulSet to control start replica ordinal numbering #3335

pwschuurman opened this issue Jun 3, 2022 · 24 comments
Assignees
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/apps Categorizes an issue or PR as relevant to SIG Apps. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Milestone

Comments

@pwschuurman
Copy link
Contributor

pwschuurman commented Jun 3, 2022

Enhancement Description

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

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jun 3, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented Sep 1, 2022

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 1, 2022
@pwschuurman
Copy link
Contributor Author

pwschuurman commented Sep 19, 2022

/sig multicluster

@k8s-ci-robot k8s-ci-robot added sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Sep 19, 2022
@JeremyOT
Copy link
Member

JeremyOT commented Sep 20, 2022

/label lead-opted-in

@k8s-ci-robot k8s-ci-robot added the lead-opted-in Denotes that an issue has been opted in to a release label Sep 20, 2022
@rhockenbury
Copy link

rhockenbury commented Sep 21, 2022

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

@k8s-ci-robot k8s-ci-robot added stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Sep 21, 2022
@k8s-ci-robot k8s-ci-robot added this to the v1.26 milestone Sep 21, 2022
@ruheenaansari34
Copy link

ruheenaansari34 commented Sep 27, 2022

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

ruheenaansari34 commented Oct 4, 2022

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

pwschuurman commented Oct 6, 2022

Hi @ruheenaansari34, #3336 has been merged.

@pwschuurman
Copy link
Contributor Author

pwschuurman commented Oct 6, 2022

/sig apps

@k8s-ci-robot k8s-ci-robot added the sig/apps Categorizes an issue or PR as relevant to SIG Apps. label Oct 6, 2022
@pwschuurman
Copy link
Contributor Author

pwschuurman commented Oct 6, 2022

/remove-sig multicluster

@k8s-ci-robot k8s-ci-robot removed the sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. label Oct 6, 2022
@rhockenbury
Copy link

rhockenbury commented Oct 6, 2022

Thanks, the enhancements team has this marked as tracked now.

@soltysh
Copy link
Contributor

soltysh commented Oct 7, 2022

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 7, 2022
@pwschuurman
Copy link
Contributor Author

pwschuurman commented Oct 8, 2022

@pwschuurman
Copy link
Contributor Author

pwschuurman commented Oct 14, 2022

Hi @ruheenaansari34 @rhockenbury, this is currently marked as tracked by sig-multicluster, but the KEP is in sig-apps. Can the enhancements spreadsheet be updated to reflect the current state of this enhancement? https://github.com/orgs/kubernetes/projects/98/views/11?sortedBy%5Bdirection%5D=asc&sortedBy%5BcolumnId%5D=15217749&filterQuery=sig%3Asig-multicluster

@rhockenbury
Copy link

rhockenbury commented Oct 15, 2022

Thanks. Fixed.

@parul5sahoo
Copy link
Member

parul5sahoo commented Nov 1, 2022

Hi @pwschuurman 👋,

Checking in once more as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 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). Open PR
  • All PRs are fully merged by the code freeze deadline.

For this enhancement, please plan to get PRs out for all k/k code so it can be merged up by code freeze. If you do have k/k PRs open, please link them to this issue. Let me know if there aren't any further PRs that need to be created or merged for this enhancements, so that I can mark it as tracked.

As always, we are here to help should questions come up. Thanks!

@cathchu
Copy link

cathchu commented Nov 2, 2022

Hi there @pwschuurman 👋 1.26 Docs Shadow here.

This enhancement is marked as ‘Needs Docs’ for 1.26 release. I see you've opened kubernetes/website#37224. I'd like to confirm that all Docs related changes will be included in this PR.

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

Thank you!

@pwschuurman
Copy link
Contributor Author

pwschuurman commented Nov 2, 2022

Hi there @pwschuurman wave 1.26 Docs Shadow here.

This enhancement is marked as ‘Needs Docs’ for 1.26 release. I see you've opened kubernetes/website#37224. I'd like to confirm that all Docs related changes will be included in this PR.

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

Thank you!

Thanks @cathchu, yes ubernetes/website/pull/37224 is the only documentation associated with this PR. I do have a blog as well, but this is tracked by the communications team.

@parul5sahoo
Copy link
Member

parul5sahoo commented Nov 7, 2022

Hey @pwschuurman,

As the Code freeze is just a day away, just wanted to confirm that there are no other open PRs in the K/K repo or any repo in general for this enhancement except for the ones outlined in the issues description? Please try to get the open PRs merged before code freeze, so that the enhancement can be marked tracked.

@pwschuurman
Copy link
Contributor Author

pwschuurman commented Nov 8, 2022

Hi @parul5sahoo, yes this is the only k/k PR. There arare two other PRs, one for documentation and one for the blog post. Working on getting the k/k PR submitted today

@parul5sahoo
Copy link
Member

parul5sahoo commented Nov 8, 2022

Please try to get it merged before Code Freeze.

@rhockenbury
Copy link

rhockenbury commented Nov 9, 2022

Hello 👋, 1.26 Enhancements Lead here.

Unfortunately, this enhancement did not meet requirements for code freeze.

If you still wish to progress this enhancement in v1.26, please file an exception request. Thanks!

/milestone clear
/label tracked/no
/remove-label tracked/yes
/remove-label lead-opted-in

@k8s-ci-robot k8s-ci-robot added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Nov 9, 2022
@k8s-ci-robot k8s-ci-robot removed this from the v1.26 milestone Nov 9, 2022
@k8s-ci-robot k8s-ci-robot removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team lead-opted-in Denotes that an issue has been opted in to a release labels Nov 9, 2022
@pwschuurman
Copy link
Contributor Author

pwschuurman commented Nov 9, 2022

Hi @rhockenbury I just filed for an exception request: https://groups.google.com/g/kubernetes-sig-apps/c/SqUMOWxwwpo

This exception is just pending on a single PR (kubernetes/kubernetes#112744), which has been signed off by sig-apps and is just pending final API review.

@leonardpahlke
Copy link
Member

leonardpahlke commented Nov 9, 2022

exception request accepted

/milestone v1.26
/label tracked/yes
/label lead-opted-in
/remove tracked/no

@k8s-ci-robot k8s-ci-robot added this to the v1.26 milestone Nov 9, 2022
@k8s-ci-robot k8s-ci-robot added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team lead-opted-in Denotes that an issue has been opted in to a release labels Nov 9, 2022
@leonardpahlke
Copy link
Member

leonardpahlke commented Nov 9, 2022

/remove-label tracked/no

@k8s-ci-robot k8s-ci-robot removed the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/apps Categorizes an issue or PR as relevant to SIG Apps. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Projects
Status: Net New
Development

No branches or pull requests

10 participants