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
4 of 8 tasks
alexanderConstantinescu opened this issue Feb 3, 2023 · 34 comments
Open
4 of 8 tasks

Kube-proxy improved ingress connectivity reliability #3836

alexanderConstantinescu opened this issue Feb 3, 2023 · 34 comments
Assignees
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/network Categorizes an issue or PR as relevant to SIG Network.
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 moved this from New, not evaluated to Pre-Alpha (we want to do this but the KEP or code is not merged yet) in Obsolete: SIG-Network KEPs (see https://github.com/orgs/kubernetes/projects/148) 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 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
@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 Jun 13, 2023

@alexanderConstantinescu
Copy link
Member Author

Thanks for the reminder, sorry for being late. Here's the PR: #4087

@aramase
Copy link
Member

aramase commented Jun 14, 2023

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 alpha for 1.28 (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: 1.28
  • KEP readme has a updated detailed test plan section filled out
  • KEP readme has up to date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

@Atharva-Shinde
Copy link
Contributor

Hey @alexanderConstantinescu

This is a nit that needs to be addressed:
Add the acknowledgement under the Test Plan section.

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.
The status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you :)

@thockin thockin modified the milestones: v1.28, v1.29 Aug 17, 2023
@alexanderConstantinescu
Copy link
Member Author

I am tracking this for beta in 1.29 - is that correct?

Yes, that is correct.

@krol3 krol3 removed the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Sep 20, 2023
@npolshakova
Copy link

npolshakova commented Sep 21, 2023

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 beta for 1.29 (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: 1.29. 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).

For this KEP, we would just need to update the following:

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

@npolshakova
Copy link

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 at risk for enhancement freeze.

It looks like #4258 will address most of the requirements. Let me know if I missed anything. Thanks!

@alexanderConstantinescu
Copy link
Member Author

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.

@npolshakova
Copy link

Looks good! This enhancement is now tracked for enhancement freeze. 🚀

@harshitasao
Copy link

Hi @alexanderConstantinescu 👋, v1.29 Docs Shadow here
Does this enhancement work planned for v1.29 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.29 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, 19 October 2023.
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

@npolshakova
Copy link

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:

  • 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.

Please update the Issue description to include all the related PRs of this KEP (including #4258) under a new beta section in the Github Issue description. The status for this KEP is currently at risk for code freeze.

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.
As always, we are here to help if any questions come up. Thanks!

@kcmartin
Copy link

kcmartin commented Oct 30, 2023

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.
The deadline will be on Tuesday 14th November 2023 (after the Docs deadline PR ready for review)

Here's the 1.29 Calendar

@npolshakova
Copy link

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 tracked for code freeze for the 1.29 Code Freeze! 🚀

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!

@salehsedghpour
Copy link
Contributor

/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 Jan 6, 2024
@salehsedghpour
Copy link
Contributor

Hello 👋 1.30 Enhancements Lead here,

I'm closing milestone 1.29 now,
If you wish to progress this enhancement in v1.30, please follow the instructions here to opt in the enhancement and make sure the lead-opted-in label is set so it can get added to the tracking board and finally add /milestone v1.30. Thanks!

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.29 milestone Jan 16, 2024
@thockin
Copy link
Member

thockin commented Jan 19, 2024

Pinging this after sig-net - let's decide if this moves to beta in 1.30

@thockin thockin added this to the v1.30 milestone Jan 23, 2024
@thockin thockin added the lead-opted-in Denotes that an issue has been opted in to a release label Jan 23, 2024
@tjons
Copy link

tjons commented Jan 31, 2024

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 beta for 1.30 (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: 1.30. 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).

For this KEP, we would just need to complete the following:

  • Complete the PRR review process and merge it into k/enhancements.

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

@alexanderConstantinescu
Copy link
Member Author

@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?

@tjons
Copy link

tjons commented Feb 1, 2024

@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 🚀

@chanieljdan
Copy link

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?
If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday February 22nd 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

@a-mccarthy
Copy link

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.
The placeholder PR deadline is 27th February, 2024.
Here's the 1.30 Release Calendar

@chanieljdan
Copy link

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? If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday February 22nd 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

Hi @alexanderConstantinescu and @thockin 👋, could you review the above before the placeholder deadline tonight? Thanks!

@alexanderConstantinescu
Copy link
Member Author

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
Status: Removed From Milestone
Status: Tracked
Status: Tracked for Code Freeze
Status: Tracked for Enhancements Freeze
Obsolete: SIG-Network KEPs (see https...
Pre-Alpha (we want to do this but the...
Development

No branches or pull requests