Skip to content
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

Open
10 of 12 tasks
alexanderConstantinescu opened this issue Feb 3, 2023 · 57 comments
Open
10 of 12 tasks

Kube-proxy improved ingress connectivity reliability #3836

alexanderConstantinescu opened this issue Feb 3, 2023 · 57 comments
Assignees
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Milestone

Comments

@alexanderConstantinescu
Copy link
Member

alexanderConstantinescu commented Feb 3, 2023

Enhancement Description

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

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Feb 3, 2023
@alexanderConstantinescu
Copy link
Member Author

/sig network

@k8s-ci-robot k8s-ci-robot added sig/network Categorizes an issue or PR as relevant to SIG Network. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 3, 2023
@thockin thockin self-assigned this Feb 3, 2023
@thockin thockin added this to the v1.27 milestone Feb 8, 2023
@thockin thockin added the lead-opted-in Denotes that an issue has been opted in to a release label Feb 8, 2023
@marosset
Copy link
Contributor

This enhancement meets all the requirements for inclusion in v1.27 and is now tracked for the release!

@marosset marosset moved this to Removed From Milestone in 1.27 Enhancements Tracking Feb 10, 2023
@marosset marosset moved this from Removed From Milestone to Tracked in 1.27 Enhancements Tracking Feb 10, 2023
@marosset marosset added stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Feb 10, 2023
@marosset
Copy link
Contributor

marosset commented Mar 8, 2023

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:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PRs are fully merged by the code freeze deadline.

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!

@taniaduggal
Copy link

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.
Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.
Please feel free to reach out with any questions. Thanks!

@marosset
Copy link
Contributor

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
/remove-label tracked/yes
/label tracked/no

@k8s-ci-robot k8s-ci-robot added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Mar 15, 2023
@k8s-ci-robot k8s-ci-robot removed this from the v1.27 milestone Mar 15, 2023
@k8s-ci-robot k8s-ci-robot removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Mar 15, 2023
@marosset marosset moved this from Tracked to Removed From Milestone in 1.27 Enhancements Tracking Mar 15, 2023
@thockin thockin added this to the v1.28 milestone Mar 15, 2023
@Atharva-Shinde Atharva-Shinde removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team lead-opted-in Denotes that an issue has been opted in to a release labels May 14, 2023
@thockin thockin added the lead-opted-in Denotes that an issue has been opted in to a release label Jun 7, 2023
@thockin
Copy link
Member

thockin commented May 23, 2024

ACK!

@thockin thockin modified the milestones: v1.30, v1.31 May 23, 2024
@ArkaSaha30
Copy link
Member

ArkaSaha30 commented Jun 4, 2024

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 stable for v1.31 (correct me, if otherwise)

Here's where this enhancement currently stands:

  • KEP readme using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable for latest-milestone: v1.31. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
  • KEP readme has up-to-date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline so that the PRR team has enough time to review your KEP before the enhancements freeze.

For this KEP, it would be good to update the following:

  • Implementation history in the KEP README

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 tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

@ArkaSaha30
Copy link
Member

/stage stable

@k8s-ci-robot k8s-ci-robot added the stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status label Jun 4, 2024
@ArkaSaha30 ArkaSaha30 moved this to Tracked for Enhancements Freeze in 1.31 Enhancements Tracking Jun 4, 2024
@Princesso
Copy link

Hello @thockin 👋, 1.31 Docs Lead here.
Does this enhancement work planned for 1.31 require any new docs or modification to existing docs?
If so, please follow 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 familiarised with the docs requirement for the release.
Thank you!

@mbianchidev
Copy link
Member

Heey @thockin , @alexanderConstantinescu

👋 from the v1.31 Communications Team!
We'd love for you to opt in to write a feature blog about your enhancement!
Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

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 XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

@Princesso
Copy link

Princesso commented Jun 24, 2024

Hello @thockin 👋, 1.31 Docs Lead here. Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? If so, please follow 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 familiarised with the docs requirement for the release. Thank you!

Hi @thockin, @alexanderConstantinescu, gentle reminder to raise a doc placeholder PR for this enhancement before Thursday June 27, 2024 18:00 PDT.

@sreeram-venkitesh sreeram-venkitesh added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jun 24, 2024
@mbianchidev
Copy link
Member

Heey @thockin , @alexanderConstantinescu

👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

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 XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

Reminder of the 3rd of July deadline!
It's totally fine to also opt out if you don't think that writing a blog is useful for our users or if you don't have time (in that case team comms can also help you out 👀 )

@natalisucks
Copy link

Hello @thockin 👋, 1.31 Docs Lead here. Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? If so, please follow 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 familiarised with the docs requirement for the release. Thank you!

Hi @thockin, @alexanderConstantinescu, gentle reminder to raise a doc placeholder PR for this enhancement before Thursday June 27, 2024 18:00 PDT.

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

@aojea
Copy link
Member

aojea commented Jun 29, 2024

@natalisucks I've opened the PR on behalf of @alexanderConstantinescu kubernetes/website#47030
not blog docs

@alexanderConstantinescu
Copy link
Member Author

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.

@ArkaSaha30
Copy link
Member

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:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

With all the implementation(code related) PRs merged as per the issue description:

This enhancement is now marked as tracked for code freeze for the 1.31 Code Freeze!

@ArkaSaha30 ArkaSaha30 moved this from Tracked for Enhancements Freeze to Tracked for Code Freeze in 1.31 Enhancements Tracking Jul 8, 2024
@Princesso Princesso moved this from Tracked for Code Freeze to Tracked for Doc Freeze in 1.31 Enhancements Tracking Jul 29, 2024
@thockin thockin moved this from 03 Beta to 04 GA in SIG Network KEPs Aug 21, 2024
@tjons
Copy link
Contributor

tjons commented Sep 7, 2024

@alexanderConstantinescu in preparation for the next release, now that this KEP has been implemented, would you kindly update the KEP status to implemented and then close this out?

@thockin
Copy link
Member

thockin commented Sep 10, 2024

FTR: gate-removal is slated for 1.33 - should we close the KEP before that?

@tjons
Copy link
Contributor

tjons commented Sep 15, 2024

@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

@k8s-ci-robot k8s-ci-robot removed this from the v1.31 milestone Sep 15, 2024
@tjons
Copy link
Contributor

tjons commented Sep 16, 2024

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

@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Sep 16, 2024
@thockin thockin added this to the v1.33 milestone Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Projects
Status: Removed From Milestone
Status: Tracked
Status: Tracked for Code Freeze
Status: Tracked for Doc Freeze
Status: GA
Status: Tracked for Doc Freeze
Development

No branches or pull requests