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
Comments
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/sig multicluster |
/label lead-opted-in |
/milestone v1.26 |
Hello @pwschuurman Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022. This enhancement is targeting for stage Here's where this enhancement currently stands:
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 |
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. |
Hi @ruheenaansari34, #3336 has been merged. |
/sig apps |
/remove-sig multicluster |
Thanks, the enhancements team has this marked as |
/remove-lifecycle stale |
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 |
Thanks. Fixed. |
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:
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 As always, we are here to help should questions come up. Thanks! |
@pwschuurman are you planning to promote this to beta in 1.27? |
@soltysh Yes, I would like to promote to beta in 1.27. Working on the testing requirements for KEP in beta. |
@soltysh Would you be able to opt this KEP in for 1.27 release milestone (https://www.kubernetes.dev/blog/2022/09/09/enhancements-opt-in/)? |
/label lead-opted-in |
@soltysh Do you mind to take a look at kubernetes/kubernetes#115468? I'd like to get the e2e tests submitted and running in testgrid (https://testgrid.k8s.io/google-gce#gci-gce-alpha-enabled-default) so we can have a clear signal prior to promoting the feature flag. |
@pwschuurman let's start with just that integration for now (from kubernetes/kubernetes#115466) as a starting point (which is already tagged and should merge shortly), and when promoting to beta and enabling the feature permanently we'll merge kubernetes/kubernetes#115468, wdyt? |
Hello @pwschuurman Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this enhancement it looks like #3768 will address all of these requirements. The status of this enhancement is marked as |
With #3768 this enhancement is ready to be |
Hi @pwschuurman Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023. Please ensure the following items are completed:
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze:
Please let me know if there are any other PRs in k/k I should be tracking for this KEP. As always, we are here to help should questions come up. Thanks! |
Hi @marosset, For this enhancement, it looks like the following PRs are open and need to be merged before code freeze:
Both of these are pending on API review for kubernetes/kubernetes#115260, but will be ready to merge after this approval.
I also have a PR in kube-state-metrics: kubernetes/kube-state-metrics#1959. I'm assuming this does not need to be merged by code freeze, since it's not in the k/k repo? |
Enhancement Description
.spec.ordinals.start
field.k/enhancements
) update PR(s): KEP-3335: StatefulSet Start Ordinal #3336k/k
) update PR(s): Add implementation of KEP-3335, StatefulSetSlice kubernetes#112744k/website
) update PR(s): Add initial documentation for StatefulSetSlice feature website#37224k/enhancements
) update PR(s): KEP-3335: Update beta milestone to 1.27 #3768k/k
) update PR(s): Move StatefulSetStartOrdinal feature gate to beta kubernetes#115260k/kube-state-metrics
) update PR(s): Add StatefulSet Start Ordinal metrics for KEP-3335 kube-state-metrics#1959k/k
) unit PR(s): Add enablement/disablement unit test for StatefulSetStartOrdinal feature kubernetes#115536k/k
) integration PR(s): Add integration tests for StatefulSetStartOrdinal feature kubernetes#115466k/k
) e2e PR(s): Add e2e tests for StatefulSetStartOrdinal feature kubernetes#115468k/website
) update(s): Update StatefulSetStartOrdinal documentation to target beta in 1.27 website#39823Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: