-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Coordinated Leader Election #4355
Comments
/sig api-machinery |
/label lead-opted-in This is targeting 1.31, but we'd like to merge the KEP early if possible so we can start implementation work. |
/assign @sttts |
/milestone v1.31 |
/milestone clear |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Hi @jpbetz @deads2k, since this KEP already had lead-opted-in label and is targeting 1.31 for alpha as mentioned above by Joe, I've not made any changes and the KEP has been added to the 1.31 enhancements tracking board. Please let me know if this works. We can add the 1.31 milestone and update the issue description as well. |
Hello @jpbetz 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024. This enhancement is targeting for stage Here’s where this enhancement currently stands:
For this KEP, we would just need to complete the following:
The status of this enhancement is marked as If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
/stage alpha |
Hi @jpbetz 👋, 1.31 Docs Shadow here. Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarized with the docs requirement for the release. Thank you! Daniel |
Hi @tjons. I just want to double check, the PRs have merged (#4703 and #4356) and this is the updated state of the KEP https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4355-coordinated-leader-election. I just want to double check that everything should be in place for alpha? Thanks! |
Hi @Jefftree - the KEP readme changes look good, but we still need to update the |
Hi @tjons PRR is merged: https://github.com/kubernetes/enhancements/blob/master/keps/prod-readiness/sig-api-machinery/4355.yaml Milestone has been updated to 1.31 and merged: #4717 |
Looks good! Will update the status to tracked for enhancements freeze |
Hi @jpbetz 👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! 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 |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
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-sigs/prow repository. |
/reopen |
@Jefftree: Reopened this issue. In response to this:
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-sigs/prow repository. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/label lead-opted-in |
KEP to Beta PR: #5088 |
Hello @jpbetz 👋, v1.33 Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025. This enhancement is targeting stage Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
Hi @jpbetz @Jefftree 👋, 1.33 Enhancements team here, Just a quick friendly reminder as we approach the enhancements freeze later this week, at 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025. The current status of this enhancement is marked as If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
Hello @jpbetz 👋, 1.33 Enhancements team here, Now that PR #5088 have 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 (cc: @ArkaSaha30) /label tracked/yes |
Hi @jpbetz @Jefftree! 👋 v1.33 Docs Shadow here. Does this enhancement work planned for v1.33 require any new docs or modification to existing docs? If so, please follow the steps here to open a PR against dev-1.33 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 27th February 2025 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you! |
Enhancement Description
k/enhancements
) update PR(s): KEP-4355: Coordinated Leader Election #4356k/k
) update PR(s):Coordinated Leader Election kubernetes#124012k/website
) update PR(s): [KEP-4355] Coordinated Leader Election alpha documentation website#46982k/enhancements
) update PR(s): Coordinated Leader Election to Beta #5088k/k
) update PR(s):k/website
) update(s):Please 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: