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

Make kube-proxy service abstraction optional #2447

Closed
4 tasks
shekhar-rajak opened this issue Feb 7, 2021 · 2 comments
Closed
4 tasks

Make kube-proxy service abstraction optional #2447

shekhar-rajak opened this issue Feb 7, 2021 · 2 comments
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network.

Comments

@shekhar-rajak
Copy link
Contributor

Enhancement Description

  • One-line enhancement description (can be used as a release note):

Make kube-proxy service abstraction optional

  • Kubernetes Enhancement Proposal:

In a cluster that has a service mesh a lot of the work being done by kube-proxy is redundant and wasted.
Specifically, services that are only reached via other services in the mesh will never use the service abstraction implemented by kube-proxy in iptables (or ipvs).
By informing the kube-proxy of this, we can lighten the work it is doing and the burden on its proxy backend.

  • Discussion Link:
  • Primary contact (assignee): @bradhoekstra @thockin
  • Responsible SIGs: sig-network
  • Enhancement target (which target equals to which milestone):
    • Alpha release target (x.y):
    • Beta release target (x.y):
    • Stable release target (x.y):
  • Alpha
    • KEP (k/enhancements) update PR(s):
    • Code (k/k) update PR(s):
    • Docs (k/website) update PR(s):

Implementation History

  • 2018-10-17 - This KEP is created
  • 2018-11-12 - KEP updated, including approver/reviewer

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 Feb 7, 2021
@shekhar-rajak
Copy link
Contributor Author

Migrating all the old template keps to new template : #2446

@kikisdeliveryservice kikisdeliveryservice added the sig/network Categorizes an issue or PR as relevant to SIG Network. label Feb 11, 2021
@k8s-ci-robot k8s-ci-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Feb 11, 2021
@thockin
Copy link
Member

thockin commented Apr 30, 2021

Implemented

@thockin thockin closed this as completed Apr 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Development

No branches or pull requests

4 participants