nftables kube-proxy backend

[danwinship]

Enhancement Description

• One-line enhancement description (can be used as a release note): Add a new kube-proxy backend using nftables
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/3866-nftables-proxy/README.md
• Discussion Link:
• Primary contact (assignee): @danwinship
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.29
  • Beta release target (x.y): 1.31
  • Stable release target (x.y): 1.33
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-3866: kube-proxy nftables mode #3824
  • Code (k/k) update PR(s): kube-proxy nftables backend kubernetes#121046
  • Docs (k/website) update PR(s): Document nftables kube-proxy alpha (KEP 3866) website#43588
• Beta
  • KEP (k/enhancements) update PR(s): KEP-3866 kube-proxy nftables to beta #4663
  • Code (k/k) update PR(s): KEP-3866 kube-proxy nftables to beta kubernetes#124383
    • belatedly update the release notes text in that PR
  • Docs (k/website) update(s): Update nftables kube-proxy docs for 1.31 beta website#46541
  • Blog post: nftables kube-proxy blog post for 1.31 website#46969
• Stable
  • KEP (k/enhancements) update PR(s): KEP-3866 nftables kube-proxy to GA #5044
  • Code (k/k) update PR(s): KEP-3866 nftables kube-proxy to GA kubernetes#129653
  • Docs (k/website) update(s): KEP-3866 nftables kube-proxy to GA website#49453
  • Blog post: nftables kube-proxy blog post for 1.33 website#49393

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

[danwinship]

/sig network

[nikzayn]

Hey, can I take this up? I would like to work on it!

/assign

[aojea]

• KEP-3866: kube-proxy nftables mode KEP-3866: kube-proxy nftables mode #3824

/unassign @nikzayn

check the description

Primary contact (assignee): @danwinship

/assign @danwinship

You can collaborate by commenting on the KEP #3824 and see if there are some tasks that can be assigned from there

[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

[danwinship]

/remove-lifecycle stale