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 |
@alexanderConstantinescu https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/3836-kube-proxy-improved-ingress-connectivity-reliability/kep.yaml still says Alpha and needs a PRR touch to move to beta |
Thanks for the reminder, sorry for being late. Here's the PR: #4087 |
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:
The status of this enhancement is marked as |
This is a nit that needs to be addressed: I won't decline this KEP for the Enhancements freeze because of this change but would be great to get a PR ready addressing them. |
Yes, that is correct. |
Hello @alexanderConstantinescu! 👋 1.29 Enhancements team here! Just checking in as we approach enhancements freeze on 01:00 UTC, 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 update the following:
The status of this enhancement is marked as |
Hi @alexanderConstantinescu, just checking in once more as we approach the 1.29 enhancement freeze deadline this week on 01:00 UTC, Friday, 6th October, 2023. The status of this enhancement is marked as It looks like #4258 will address most of the requirements. Let me know if I missed anything. Thanks! |
Hi @npolshakova ! 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. |
Looks good! This enhancement is now |
Hi @alexanderConstantinescu 👋, v1.29 Docs Shadow here |
Hey again @alexanderConstantinescu 👋, 1.29 Enhancements team here, Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 2023: . Here's where this enhancement currently stands:
Please update the Issue description to include all the related PRs of this KEP (including #4258) under a new Also, please let me know if there are 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 #4258 merged, all the tracked implementation(code related) PRs are merged as per the issue description and 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. Please let me know if there are any test PRs we should track. Thanks! |
/remove-label lead-opted-in |
Hello 👋 1.30 Enhancements Lead here, I'm closing milestone 1.29 now, /milestone clear |
Pinging this after sig-net - let's decide if this moves to beta in 1.30 |
Hello @alexanderConstantinescu 👋, Enhancements team here. Just checking in as we approach enhancements freeze on Friday, February 9th, 2024 at 02:00 UTC. 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 |
@tjons : I made a mistake in the last release and got a prr-review for Beta, but forgot to update the code afterwards. In this release we're only updating the code and the prr-review file already exists, see: https://github.com/kubernetes/enhancements/blob/master/keps/prod-readiness/sig-network/3836.yaml Is this fine? |
@alexanderConstantinescu thanks for the update! This should be fine... With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀 |
Hi @alexanderConstantinescu and @thockin 👋, 1.30 Docs Shadow here. Does this enhancement work planned for 1.30 require any new docs or modification to existing docs? Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you! |
Hi @alexander-demicev and @thockin, 👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating. To opt in, you need to open a Feature Blog placeholder PR against the website repository. |
Hi @alexanderConstantinescu and @thockin 👋, could you review the above before the placeholder deadline tonight? Thanks! |
@chanieljdan : sorry for the delay! It was indeed agreed that this enhancement should result in a document written in https://kubernetes.io/docs/concepts/. Here's a placeholder PR I created for this: kubernetes/website#45290 What is the deadline for the final docs PR to merge for 1.30? |
Hey again @alexanderConstantinescu 👋 Enhancements team here, Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 . Here's where this enhancement currently stands:
For this enhancement, it looks like the linked PR is already approved and merged and has the appropriate labels, so I believe you are good to go. Please let me know if there are other PRs in k/k we should be tracking for this KEP. |
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.
/sig-network
/cc @thockin @danwinship
The text was updated successfully, but these errors were encountered: