Kube-proxy Services Acceleration

[aojea]

Enhancement Description

• One-line enhancement description (can be used as a release note): Service acceleration for Kube-proxy using netfilter’s flowtable infrastructure
• Kubernetes Enhancement Proposal: KEP-4963: Kube-proxy Services Acceleration #4964
• Discussion Link: [WIP] KEP-4963: Kube-proxy Services Acceleration kubernetes#128392
• Primary contact (assignee): aojea
• Responsible SIGs: SIG-Network
• Enhancement target (which target equals to which milestone):
  • Alpha release target: 1.33
  • Beta release target: 1.34
  • Stable release target: 1.35
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-4963: Kube-proxy Services Acceleration #4964
  • Code (k/k) update PR(s): [WIP] KEP-4963: Kube-proxy Services Acceleration kubernetes#128392
  • Docs (k/website) update PR(s):

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages issues 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:

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

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

/close not-planned