-
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
Kube-proxy improved ingress connectivity reliability #3836
Comments
/sig network |
This enhancement meets all the requirements for inclusion in v1.27 and is now |
Hi @alexanderConstantinescu 👋, 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:
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 @alexanderConstantinescu 👋 , I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release. |
Unfortunately the implementation PRs associated with this enhancement have not merged by code-freeze so this enhancement is getting removed from the release. If you would like to file an exception please see https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md /milestone clear |
ACK! |
Hello @thockin 👋, 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 stage Here's where this enhancement currently stands:
For this KEP, it would be good to update the following:
Other than this, 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 |
/stage stable |
Hello @thockin 👋, 1.31 Docs Lead here. |
Heey @thockin , @alexanderConstantinescu 👋 from the v1.31 Communications Team! 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 |
Hi @thockin, @alexanderConstantinescu, gentle reminder to raise a doc placeholder PR for this enhancement before Thursday June 27, 2024 18:00 PDT. |
Reminder of the 3rd of July deadline! |
Howdy @thockin, @alexanderConstantinescu, SIG Docs co-chair here 👋 I wanted to add another reminder about the docs deadline for this enhancement: updating feature gates qualifies as requiring documentation as far as Release Docs is concerned, so please check out @Princesso's reminder above to ensure you meet the deadline today |
@natalisucks I've opened the PR on behalf of @alexanderConstantinescu kubernetes/website#47030 |
Hi! Sorry for the confusion, I was away on vacation for the past two weeks. I've filed: kubernetes/website#47048 which will supersede @aojea's PR. |
Hello again @thockin 👋, 1.31 Enhancements team here, Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024. Here's where this enhancement currently stands:
With all the implementation(code related) PRs merged as per the issue description: This enhancement is now marked as |
@alexanderConstantinescu in preparation for the next release, now that this KEP has been implemented, would you kindly update the KEP status to |
FTR: gate-removal is slated for 1.33 - should we close the KEP before that? |
@thockin I'll just remove it from the 1.31 milestone and then we can close it once the gate-removal is complete /milestone clear |
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 |
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):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.
/sig-network
/cc @thockin @danwinship
The text was updated successfully, but these errors were encountered: