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
Remove transient node predicates from KCCM's service controller #3458
Comments
/sig network |
Punting to 1.27 |
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 |
/label lead-opted-in |
/retitle Remove transient node predicates from KCCM's service controller |
@thockin @alexanderConstantinescu can one of you confirm that this targeting |
Yes, that is correct and what we've discussed / agreed on the KEP. Maybe @thockin wants to give the final confirmation? |
yes please - this one doesn't have APi so doesn't need an alpha |
Thanks @thockin @alexanderConstantinescu |
Once #3835 merges this enhancement will be ready for inclusion in v1.27 |
With #3835 merged this enhancement is ready to be |
Hi @thockin 👋,
Please let me know what PRs in k/k I should be tracking for this KEP. |
Hello @alexanderConstantinescu 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 01:00 UTC Friday, 16th June 2023. This enhancement is targeting for 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 |
@alexanderConstantinescu https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/3458-remove-transient-node-predicates-from-service-controller/kep.yaml still says "beta" and needs final PRR signoff (thanks, @wojtek-t for the poke) |
Sorry for the late reply to this: the KEP says GA in 1.29 that isn't advanced to 1.28 just because the release went well, right? |
Thanks for the reminder! Here's the PR: #4088 I didn't update the stable milestone because of I mentioned above |
Sorry, somehow I thought it was GA this release. Milestone bumped |
Hello @thockin @alexanderConstantinescu 👋, 1.28 Docs Lead here. Does this enhancement work planned for 1.28 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you! |
@Rishit-dagli : sorry for the late reply
No, it does not. |
Hey again @alexanderConstantinescu 👋
Please keep the issue description up-to-date with all the PR/s that are associated with this KEP and let me know if there are other PR/s in k/k we should be tracking for this KEP. |
Hey @alexanderConstantinescu 👋 Enhancements Lead here, |
I am tracking this for GA in 1.29 - is that correct? |
Yes, that is correct. |
Hello @alexanderConstantinescu 👋, Enhancements team here. Just checking in as we approach enhancements freeze on Friday, 6th October 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would just need to add/update the following:
The status of this enhancement is marked as |
I think this PR needs a metadata bump like https://github.com/kubernetes/enhancements/pull/4088/files |
Hello @alexanderConstantinescu 👋, checking in once more as we approach the 1.29 enhancement freeze deadline on 01:00 UTC, Friday, 6th October, 2023. The status of this enhancement is marked as at Please let me know if I missed anything. I would like to also ask to keep the issue description up-to-date with proper information such as the link to the merged PR. |
Hi @salehsedghpour ! That PR has merged and should fulfill all necessary requirements for progressing this KEP to the next phase. Let me know if anything is missing, but this KEP should be ready now for the next Kube release. |
Hi @alexanderConstantinescu, thanks for the update. the status is now |
Hi @alexanderConstantinescu 👋, v1.29 Docs Shadow here |
Hey again @alexanderConstantinescu 👋 Enhancements team here, Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November. Here's where this enhancement currently stands:
Please update the Issue description to include all the related PRs (including kubernetes/kubernetes#121091, I guess) of this KEP under a new Also, please let me know if there are any other PRs in k/k we should be tracking for this KEP. |
Hi @alexanderConstantinescu ! 👋 from the v1.29 Release Team-Communications! We would like to check if you have any plans to publish a blog for this KEP regarding new features, removals, and deprecations for this release. If so, you need to open a PR placeholder in the website repository. |
Hello @alexanderConstantinescu 👋, 1.29 Enhancements team here. With all the implementation(code related) PRs merged as per the issue description, this enhancement is now marked as The test freeze is 01:00 UTC Wednesday 15th November 2023 / 18:00 PDT Tuesday 14th November 2023. Please make sure all test PRs are merged in by then. The tracked test PRs for this KEP are: Please let me know if there are additional test PRs we should track. Thanks! |
Enhancement Description
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):k/enhancements
) update PR(s):k/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: