KEP-2104: kube-proxy v2: reworking the proxy's architecture #2094

mcluseau · 2020-10-10T23:06:33Z

Hi folks,

I started the process of writing the KEP for my proposal of a "kube-proxy v2", and I think I'm ready to get some early comments. Thanks in advance for kind reviews and ideas :-)

@thockin

k8s-ci-robot · 2020-10-10T23:06:41Z

Welcome @mcluseau!

It looks like this is your first PR to kubernetes/enhancements 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/enhancements has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

k8s-ci-robot · 2020-10-10T23:06:41Z

Hi @mcluseau. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

danwinship

In general I like it.

keps/sig-network/20201010-kube-proxy-v2/README.md

mcluseau

Thanks for this first review, it's really nice to have external viewpoints :)

keps/sig-network/20201010-kube-proxy-v2/README.md

mcluseau · 2020-10-19T14:14:16Z

keps/sig-network/20201010-kube-proxy-v2/README.md

+This KEP is born from the conviction that more decoupling of the Service object and the actual implementations is required,
+by introducing an intermediate, node-level abstaction provider. This abstraction is expected to be the result of applying
+Kubernetes' `Service` semantics and business logic to a simpler, more stable API.
+


yes, good example of the interest of the decoupling I'm trying to achieve. Same idea with adding the topology concept.

keps/sig-network/20201010-kube-proxy-v2/README.md

keps/sig-network/2104-reworking-kube-proxy-architecture/README.md

robscott · 2020-11-04T17:57:38Z

/cc

keps/sig-network/2104-reworking-kube-proxy-architecture/README.md

thockin · 2020-12-09T21:56:53Z

That's next Monday, yes? I am in.

…

On Wed, Dec 9, 2020 at 1:52 PM Mikaël Cluseau ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In keps/sig-network/2104-reworking-kube-proxy-architecture/README.md <#2094 (comment)> : > + + + +Rewrite the kube-proxy to be a "localhost" gRPC API provider that will be accessible as usual via +TCP (`127.0.0.1:12345`) and/or via a socket (`unix:///path/to/proxy.sock`). + +- it will connect to the API server and watch resources, like the current proxy; +- then, it will process them, applying Kubernetes specific business logic like topology computation + relative to the local host; +- finally, provide the result of this computation to client via a gRPC watchable API. update: the best choice is currently on 14th at 22:30 UTC (14:30 PST) — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#2094 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKWAVAP56SDRVRNV4OHSETST7WSFANCNFSM4SLLSI3Q> .

mattklein123 · 2020-12-09T22:12:09Z

That should work for me also. Let me know the invite details.

htuch · 2020-12-09T22:14:26Z

Works for me.

mcluseau · 2020-12-09T23:41:41Z

yes, it's next monday, I'll post the link. I'll use meet unless there's a strong preference for zoom.

howardjohn · 2020-12-14T18:31:13Z

@mcluseau is this still on for today? Is there any info on the meeting address?

mcluseau · 2020-12-14T18:57:15Z

@howardjohn yes it's still today, I'll post the link here in 3h (30 min before the meeting)

mcluseau · 2020-12-14T21:57:35Z

hi all, meeting link: meet.google.com/jjf-szrn-qre

…paration of the APIServer uplink

jayunit100 · 2022-10-14T21:01:58Z

Were going to break this KEP into 3 sections , per conv w others today in sig-network

GRPC API
Process for migrating into /staging
Performance, Scale, and Conformance testing

Then we'll resubmit to Sig-network

k8s-triage-robot · 2023-01-12T21:40:51Z

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot · 2023-02-11T22:21:41Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

Mark this PR as fresh with /remove-lifecycle rotten
Close this PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot · 2023-03-13T23:17:30Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

Reopen this PR with /reopen
Mark this PR as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

k8s-ci-robot · 2023-03-13T23:17:35Z

@k8s-triage-robot: Closed this PR.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied

After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

Reopen this PR with /reopen

Mark this PR as fresh with /remove-lifecycle rotten

Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.

knabben · 2023-04-04T18:12:54Z

/reopen
/remove-lifecycle rotten

k8s-ci-robot · 2023-04-04T18:13:06Z

@knabben: Reopened this PR.

In response to this:

/reopen
/remove-lifecycle rotten

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.

k8s-ci-robot · 2023-04-04T18:13:25Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mcluseau
Once this PR has been reviewed and has the lgtm label, please ask for approval from thockin. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

keps/sig-network/OWNERS

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

k8s-triage-robot · 2023-07-03T19:12:34Z

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

Mark this PR as fresh with /remove-lifecycle stale
Close this PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

liangyuanpeng · 2023-08-20T12:13:34Z

/lifecycle frozen

k8s-ci-robot · 2023-08-20T12:13:35Z

@liangyuanpeng: The lifecycle/frozen label cannot be applied to Pull Requests.

In response to this:

/lifecycle frozen

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.

k8s-triage-robot · 2024-01-19T07:01:45Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

Mark this PR as fresh with /remove-lifecycle rotten
Close this PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

thockin · 2024-01-29T21:01:42Z

Time to close this now? I think the nftables KEP supersedes.

k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Oct 10, 2020

k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Oct 10, 2020

k8s-ci-robot requested review from caseydavenport and thockin October 10, 2020 23:06

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. labels Oct 10, 2020

mcluseau changed the title ~~[DO-NOT-MERGE] [WIP] 20201010-kube-proxy-v2: initial commit~~ [DO-NOT-MERGE] [WIP] 20201010 kube-proxy v2: reworking the proxy's architecture Oct 10, 2020

danwinship reviewed Oct 19, 2020

View reviewed changes

mcluseau commented Oct 19, 2020

View reviewed changes

mcluseau mentioned this pull request Oct 19, 2020

reworking the kube-proxy's architecture #2104

Closed

mcluseau force-pushed the master branch from b15ce15 to dbd4597 Compare October 19, 2020 14:57

mcluseau requested a review from danwinship October 19, 2020 14:58

aojea reviewed Oct 21, 2020

View reviewed changes

keps/sig-network/2104-reworking-kube-proxy-architecture/README.md Show resolved Hide resolved

aojea reviewed Oct 21, 2020

View reviewed changes

keps/sig-network/2104-reworking-kube-proxy-architecture/README.md Show resolved Hide resolved

aojea reviewed Oct 21, 2020

View reviewed changes

keps/sig-network/2104-reworking-kube-proxy-architecture/README.md Show resolved Hide resolved

aojea reviewed Oct 21, 2020

View reviewed changes

keps/sig-network/2104-reworking-kube-proxy-architecture/README.md Outdated Show resolved Hide resolved

k8s-ci-robot requested a review from robscott November 4, 2020 17:57

brb reviewed Nov 18, 2020

View reviewed changes

keps/sig-network/2104-reworking-kube-proxy-architecture/README.md Outdated Show resolved Hide resolved

thockin self-assigned this Nov 22, 2020

jayunit100 added 5 commits October 7, 2022 14:40

Add user story that clarifies the performance tuning available via se…

d6767c2

…paration of the APIServer uplink

add user story about new languages

5988636

Update README.md

7bd05dc

Update README.md

081361b

update TOC

599a2ef

astoycos mentioned this pull request Oct 24, 2022

[WIP] Make KPNG more like a library and decouple from the GRPC API kubernetes-retired/kpng#389

Closed

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 12, 2023

astoycos mentioned this pull request Feb 2, 2023

KEP-3786: Migrate Shared Kube-Proxy code into staging #3788

Closed

k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 11, 2023

k8s-ci-robot closed this Mar 13, 2023

k8s-ci-robot reopened this Apr 4, 2023

k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Apr 4, 2023

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 3, 2023

k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 19, 2024

thockin closed this Jan 29, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

KEP-2104: kube-proxy v2: reworking the proxy's architecture #2094

KEP-2104: kube-proxy v2: reworking the proxy's architecture #2094

mcluseau commented Oct 10, 2020

k8s-ci-robot commented Oct 10, 2020

k8s-ci-robot commented Oct 10, 2020

danwinship left a comment

mcluseau left a comment

mcluseau Oct 19, 2020

robscott commented Nov 4, 2020

thockin commented Dec 9, 2020 via email

mattklein123 commented Dec 9, 2020

htuch commented Dec 9, 2020

mcluseau commented Dec 9, 2020

howardjohn commented Dec 14, 2020

mcluseau commented Dec 14, 2020

mcluseau commented Dec 14, 2020

jayunit100 commented Oct 14, 2022

k8s-triage-robot commented Jan 12, 2023

k8s-triage-robot commented Feb 11, 2023

k8s-triage-robot commented Mar 13, 2023

k8s-ci-robot commented Mar 13, 2023

knabben commented Apr 4, 2023

k8s-ci-robot commented Apr 4, 2023

k8s-ci-robot commented Apr 4, 2023

k8s-triage-robot commented Jul 3, 2023

liangyuanpeng commented Aug 20, 2023

k8s-ci-robot commented Aug 20, 2023

k8s-triage-robot commented Jan 19, 2024

thockin commented Jan 29, 2024

KEP-2104: kube-proxy v2: reworking the proxy's architecture #2094

KEP-2104: kube-proxy v2: reworking the proxy's architecture #2094

Conversation

mcluseau commented Oct 10, 2020

k8s-ci-robot commented Oct 10, 2020

k8s-ci-robot commented Oct 10, 2020

danwinship left a comment

Choose a reason for hiding this comment

mcluseau left a comment

Choose a reason for hiding this comment

mcluseau Oct 19, 2020

Choose a reason for hiding this comment

robscott commented Nov 4, 2020

thockin commented Dec 9, 2020 via email

mattklein123 commented Dec 9, 2020

htuch commented Dec 9, 2020

mcluseau commented Dec 9, 2020

howardjohn commented Dec 14, 2020

mcluseau commented Dec 14, 2020

mcluseau commented Dec 14, 2020

jayunit100 commented Oct 14, 2022

k8s-triage-robot commented Jan 12, 2023

k8s-triage-robot commented Feb 11, 2023

k8s-triage-robot commented Mar 13, 2023

k8s-ci-robot commented Mar 13, 2023

knabben commented Apr 4, 2023

k8s-ci-robot commented Apr 4, 2023

k8s-ci-robot commented Apr 4, 2023

k8s-triage-robot commented Jul 3, 2023

liangyuanpeng commented Aug 20, 2023

k8s-ci-robot commented Aug 20, 2023

k8s-triage-robot commented Jan 19, 2024

thockin commented Jan 29, 2024