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
Make Kubernetes aware of the LoadBalancer behaviour #1860
Comments
/sig network |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Hi @Sh4d1 1.20 Enhancements Lead here. This KEP still seems to be a draft (it's provisional) but wanted to check-in to see if you thought this would be graduating alpha in 1.20? Enhancements Freeze is October 6th and by that time we require: The KEP must be merged in an implementable state Best, |
Note: this provisional kep was implemented without having a compliant kep or indicating to the enhancements team that it would be in the 1.20 milestone. |
👋 1.20 release lead here. We're really close to code freeze at this point (Thursday) and it seems like this KEP fell through the cracks and the process. Based on this comment in the PR above: kubernetes/kubernetes#92312 (comment) can we not land this in 1.20 and instead target 1.21? There are few things w/ the KEP that really should be address:
Looks like there is also a PR to update the KEP https://github.com/kubernetes/enhancements/pull/2134/files that addresses this stuff, however it also marks it as implemented and targets 1.21. Typically, we set to implemented only after the release. Can we circle back around on this and agree that we should try to land this in 1.21 at this point? We've already got a lot of content for the release so far (sig-docs has their work cut out for themselves!!!), we're two days out from code freeze, we have these disconnects mentioned above? |
@jeremyrickard just opened kubernetes/kubernetes#96454 to revert it, sorry again! |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
@fejta-bot: Closing 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/test-infra repository. |
/reopen |
@Sh4d1: 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/test-infra repository. |
Hello @RyanAoh 👋, v1.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:
With all the KEP requirements 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 |
Hi @Sh4d1 👋, v1.29 Docs Shadow here |
Hey again @RyanAoh 👋 v1.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:
For this enhancement, it looks like the following PRs has been merged before code freeze. Please update the issue description with the PR. Currently marking the KEP as Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. |
@sreeram-venkitesh I can't update the issue description since I'm not the author for this. Just comment here.
and the one for doc: |
Or do I need to open a new issue for it? |
@RyanAoh This is fine, you don't need to open a different issue. Thanks for the quick update! |
Hi @RyanAoh ! 👋 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. |
/remove-label lead-opted-in |
Hello 👋 1.30 Enhancements Lead here, I'm closing milestone 1.29 now, /milestone clear |
Hi @RyanAoh - are you shooting for beta in 1.30? |
@thockin Sorry for the delayed response. I've just returned to work after completing my leave. It's a bit late to progress this in v1.30. I'll aim to include it in v1.31. |
/label lead-opted-in |
Hey again @RyanAoh and @thockin 👋 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 following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP): With this, it is now marked as Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. |
@salehsedghpour @aojea is reviewing it :) as neither me or @RyanAoh have access to edit the issue, we need someone with write access to do it and add thePR :/ thanks |
@salehsedghpour 👋 I think we can move out of "Risk for Code freeze", right? Thanks! |
@rikatz with kubernetes/kubernetes#123418 being merged, this can now be marked as Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. |
Enhancement Description
Alpha release target (1.29)
Beta release target (1.30)
Stable release target (x.y)
Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement
The text was updated successfully, but these errors were encountered: