search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.33k stars 1.44k forks source link

Minimizing iptables-restore input size #3453

Closed danwinship closed 5 months ago

danwinship commented 1 year ago

Enhancement Description

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

danwinship commented 1 year ago

/sig network

aojea commented 1 year ago

/label lead-opted-in

aojea commented 1 year ago

sudo @thockin /label lead-opted-in

k8s-ci-robot commented 1 year ago

@aojea: Can not set label lead-opted-in: Must be member in one of these teams: [release-team-enhancements sig-api-machinery-leads sig-apps-leads sig-architecture-leads sig-auth-leads sig-autoscaling-leads sig-cli-leads sig-cloud-provider-leads sig-cluster-lifecycle-leads sig-contributor-experience-leads sig-docs-leads sig-instrumentation-leads sig-k8s-infra-leads sig-multicluster-leads sig-network-leads sig-node-leads sig-release-leads sig-scalability-leads sig-scheduling-leads sig-security-leads sig-storage-leads sig-testing-leads sig-windows-leads]

In response to [this](https://github.com/kubernetes/enhancements/issues/3453#issuecomment-1258597034): >/label lead-opted-in Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
rhockenbury commented 1 year ago

/label lead-opted-in /milestone v1.26 /label tracked/yes /stage alpha /kind kep

ruheenaansari34 commented 1 year ago

Hello @danwinship 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage alpha for 1.26 (correct me, if otherwise)

Here's where this enhancement currently stands:

For this KEP, we would just need to merge https://github.com/kubernetes/enhancements/pull/3454, which will take care of above requirements.

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!

thockin commented 1 year ago

Candidate for Alpha in 1.26

danwinship commented 1 year ago

@ruheenaansari34 #3454 is merged. Can you confirm that we are OK for Alpha?

ruheenaansari34 commented 1 year ago

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

parul5sahoo commented 1 year ago

Hi @danwinship 👋,

Checking in once more as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022.

Please ensure the following items are completed:

For this enhancement, open PR. Please plan to get PRs out for all k/k code so it can be merged up by code freeze. If you do have k/k PRs open, please link them to this issue. Let me know if there aren't any further PRs that need to be created or merged for this enhancements, so that I can mark it as tracked for code freeze.

As always, we are here to help should questions come up. Thanks!

cathchu commented 1 year ago

Hi there @danwinship 👋 1.26 Docs Shadow here.

This enhancement is marked as ‘Needs Docs’ for 1.26 release. I see you've opened https://github.com/kubernetes/website/pull/37649. I'd like to confirm that all Docs related changes will be included in this PR.

If not, please follow the steps detailed in the documentation to open a PR against dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by November 9. Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

parul5sahoo commented 1 year ago

Hey @danwinship ,

As the Code freeze is just a day away, just wanted to confirm that there are no open PRs in the K/K repo or any repo in general for this enhancement other than the ones outlined in the issues description? So that the enhancement can be marked tracked.

danwinship commented 1 year ago

@parul5sahoo There is nothing more to be merged to k/k, but the KEP graduation criteria said we'd enable the feature in some of the periodic scale tests, which has not yet happened. But I guess that would be due by next week's Test Freeze, not tomorrow's Code Freeze, right?

krol3 commented 1 year ago

Here another relevant doc-PR https://github.com/kubernetes/website/pull/36675 related this KEP

marosset commented 1 year ago

/remove-label lead-opted-in /remove-label tracked/yes /label tracked/no /milestone clear

thockin commented 1 year ago

This is a fairly high-risk change, which is why we did a KEP. Beta may be pointless?

thockin commented 1 year ago

@danwinship still shooting to advance in 27?

danwinship commented 1 year ago

yes. updated the checklist; all that's left for 1.27 is docs

thockin commented 1 year ago

/label lead-opted-in

marosset commented 1 year ago

Hello {enhancement owner} 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage beta for v1.27 (correct me, if otherwise)

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

/stage beta /label tracked/yes /remove-label tracked/no

marosset commented 1 year ago

Hi @danwinship :wave:,

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!

taniaduggal commented 1 year ago

Hi @danwinship 👋 , 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!

danwinship commented 1 year ago

This enhancement is marked as ‘Needs Docs’ for the 1.27 release.

There is already a docs PR filed (https://github.com/kubernetes/website/pull/39188). It was waiting for dev-1.27 to be updated for a while but it's rebased now and can be merged once it's approved.

thockin commented 1 year ago

NEXT: Aiming for GA in 1.28

Atharva-Shinde commented 1 year ago

Hello @danwinship 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on Thursday, 16th June 2023.

Looks like this enhancement is targeting for stage stable for v1.28 (correct me if otherwise)

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

Atharva-Shinde commented 1 year ago

/stage stable

Atharva-Shinde commented 12 months ago

Hey again @danwinship :wave:

Just checking in as we approach Code freeze at 01:00 UTC Friday, 19th July 2023 .

Here’s the enhancement’s state for the upcoming code freeze:

These are the code related PR/s that I found on this KEP issue:

Please keep the issue description up-to-date with all the PR/s that are associated with this KEP and let me know if there are other PR/s in k/k we should be tracking for this KEP.

As always, we are here to help if any questions come up. Thanks!

Atharva-Shinde commented 11 months ago

Hey @danwinship 👋 Enhancements Lead here, With https://github.com/kubernetes/kubernetes/pull/117787 and https://github.com/kubernetes/kubernetes/pull/117872 merged as per the issue description, this enhancement is now tracked for v1.28 Code Freeze. Thanks!

npolshakova commented 10 months ago

Hey @danwinship 👋 1.29 Enhancements Lead here, is there any more work planned for this KEP? Also is the milestone accurate (are you targeting v1.30 instead of v1.29?)

npolshakova commented 10 months ago

/remove-label lead-opted-in

danwinship commented 10 months ago

@npolshakova I'm not sure this needs to be tracked by the release team at this point, since it is already GA. The issue is just being left open to remind us to finish the cleanup 2 releases post-GA (so yes, the next expected change is in 1.30, not 1.29).

salehsedghpour commented 5 months ago

/milestone clear

danwinship commented 5 months ago

implemented, and feature gate removed