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

Minimizing iptables-restore input size #3453

Open
4 tasks done
danwinship opened this issue Aug 2, 2022 · 14 comments
Open
4 tasks done

Minimizing iptables-restore input size #3453

danwinship opened this issue Aug 2, 2022 · 14 comments
Assignees
Labels
kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory 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. 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
Milestone

Comments

@danwinship
Copy link
Contributor

danwinship commented Aug 2, 2022

Enhancement Description

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

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Aug 2, 2022
@danwinship
Copy link
Contributor Author

danwinship commented Aug 2, 2022

/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 Aug 2, 2022
@thockin thockin added this to New, not evaluated in SIG-Network KEPs via automation Sep 9, 2022
@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 SIG-Network KEPs Sep 9, 2022
@aojea
Copy link
Member

aojea commented Sep 26, 2022

/label lead-opted-in

@aojea
Copy link
Member

aojea commented Sep 26, 2022

sudo @thockin /label lead-opted-in

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Sep 26, 2022

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

/label lead-opted-in

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.

@rhockenbury
Copy link

rhockenbury commented Sep 27, 2022

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

@k8s-ci-robot k8s-ci-robot added stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory lead-opted-in Denotes that an issue has been opted in to a release labels Sep 27, 2022
@k8s-ci-robot k8s-ci-robot added this to the v1.26 milestone Sep 27, 2022
@k8s-ci-robot k8s-ci-robot added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Sep 27, 2022
@ruheenaansari34
Copy link

ruheenaansari34 commented Sep 28, 2022

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:

  • KEP readme using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable for latest-milestone: 1.26
  • 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.

For this KEP, we would just need to merge #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
Copy link
Member

thockin commented Sep 29, 2022

Candidate for Alpha in 1.26

@danwinship
Copy link
Contributor Author

danwinship commented Oct 4, 2022

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

@ruheenaansari34
Copy link

ruheenaansari34 commented Oct 4, 2022

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

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
Copy link
Member

parul5sahoo commented Nov 1, 2022

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:

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

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
Copy link

cathchu commented Nov 2, 2022

Hi there @danwinship 👋 1.26 Docs Shadow here.

This enhancement is marked as ‘Needs Docs’ for 1.26 release. I see you've opened kubernetes/website#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!

@thockin thockin moved this from Pre-Alpha (we want to do this but the KEP or code is not merged yet) to Alpha gated (code is merged) in SIG-Network KEPs Nov 3, 2022
@parul5sahoo
Copy link
Member

parul5sahoo commented Nov 7, 2022

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
Copy link
Contributor Author

danwinship commented Nov 7, 2022

@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
Copy link

krol3 commented Nov 28, 2022

Here another relevant doc-PR kubernetes/website#36675 related this KEP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory 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. 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
Projects
Status: Net New
SIG-Network KEPs
Alpha gated (code is merged)
Development

No branches or pull requests

9 participants