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

KEP-1860 - Propose beta graduation and add missing PRR #4509

Merged
merged 6 commits into from
Feb 19, 2024

Conversation

rikatz
Copy link
Contributor

@rikatz rikatz commented Feb 9, 2024

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Feb 9, 2024
@k8s-ci-robot k8s-ci-robot added kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory sig/network Categorizes an issue or PR as relevant to SIG Network. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 9, 2024
@rikatz
Copy link
Contributor Author

rikatz commented Feb 9, 2024

/assign @RyanAoh
Ryan, sorry for doing this "takeover'ish", just wanted to see if we can still get this as beta on v1.30.

Feel free to refuse it, or otherwise use any of the additions here on your original KEP proposal.

Thanks!

Copy link
Contributor

@danwinship danwinship left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to update kep.yaml and keps/prod-readiness/sig-network/1860.yaml too

keps/sig-network/1860-kube-proxy-IP-node-binding/README.md Outdated Show resolved Hide resolved
keps/sig-network/1860-kube-proxy-IP-node-binding/README.md Outdated Show resolved Hide resolved
keps/sig-network/1860-kube-proxy-IP-node-binding/README.md Outdated Show resolved Hide resolved
keps/sig-network/1860-kube-proxy-IP-node-binding/README.md Outdated Show resolved Hide resolved
keps/sig-network/1860-kube-proxy-IP-node-binding/README.md Outdated Show resolved Hide resolved
keps/sig-network/1860-kube-proxy-IP-node-binding/README.md Outdated Show resolved Hide resolved
keps/sig-network/1860-kube-proxy-IP-node-binding/README.md Outdated Show resolved Hide resolved
keps/sig-network/1860-kube-proxy-IP-node-binding/README.md Outdated Show resolved Hide resolved
keps/sig-network/1860-kube-proxy-IP-node-binding/README.md Outdated Show resolved Hide resolved
@rikatz
Copy link
Contributor Author

rikatz commented Feb 12, 2024

/cc @wojtek-t

@wojtek-t sorry for tagging you, as the previous PRR reviewer for this, if possible can you take a look? Thanks!!

@wojtek-t wojtek-t self-assigned this Feb 12, 2024
Copy link
Contributor

@danwinship danwinship left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm... some of my comments before may have been slightly confused because I was thinking of this as a feature that the user opted into, rather than a feature that the CloudProvider decides whether or not to use.

@danwinship
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 14, 2024
@rikatz
Copy link
Contributor Author

rikatz commented Feb 14, 2024

@wojtek-t as Dan approved it, can we now take a look into the PRR (once you have time!). Thanks!!

@wojtek-t
Copy link
Member

I'm sorry for delay - will get to it tomorrow morning.

@kikisdeliveryservice kikisdeliveryservice changed the title 1860 - Propose beta graduation and add missing PRR KEP-1860 - Propose beta graduation and add missing PRR Feb 15, 2024
Copy link
Member

@wojtek-t wojtek-t left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rikatz - sorry for delay, added few comment - other than that LGTM

keps/sig-network/1860-kube-proxy-IP-node-binding/README.md Outdated Show resolved Hide resolved
Longer term, we may want to require automated upgrade/rollback tests, but we
are missing a bunch of machinery and tooling and can't do that now.
-->
No.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should test that before enabling Beta by default.
Can you please describe the scenario here now (and ensure that you actually run it - manual run is fine) before enabling beta?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will do next here, will keep this thread open and close once I have results

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wojtek-t did the test here. Just a node (that I have added to the KEP), because this feature is mostly related to cloud providers, the test I did was, on a 3 node KinD cluster, enabled the feature flag, installed MetalLB as the LB, ran some tests, and disabled the Feature flag to check how kube-proxy and apiserver would behave.

It is registered on the steps, let me know if you need something else.

keps/sig-network/1860-kube-proxy-IP-node-binding/README.md Outdated Show resolved Hide resolved
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 18, 2024
* Confirmed that both iptables rules are present, even if the `ipMode` field was still
set as `Proxy`, confirming the feature is disabled. Both accesses are working

Additionally, an apiserver and kube-proxy upgrade test was executed as the following:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wojtek-t added the additional test of v1.28 -> v1.29 -> v1.28 and worked fine. All tests were executed with KinD and metallb.

@wojtek-t
Copy link
Member

Thank you - this looks great now!

/lgtm
/approve PRR

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 19, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danwinship, rikatz, wojtek-t

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 19, 2024
@k8s-ci-robot k8s-ci-robot merged commit f539d1c into kubernetes:master Feb 19, 2024
4 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.30 milestone Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/network Categorizes an issue or PR as relevant to SIG Network. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants