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

[npolshakova]

Hi @danwinship, 1.29 Enhancements team here! Is this enhancement targeting 1.29? If it is, can you follow the instructions here to opt in the enhancements and make sure the lead-opted-in label is set so it can get added to the tracking board? Thanks!

[wojtek-t]

/label lead-opted-in

[npolshakova]

Hi @danwinship 👋, 1.29 Enhancements team here!

Just checking in as we approach enhancements freeze on 01:00 UTC, Friday, 6th October, 2023.

This enhancement is targeting for stage alpha for 1.29 (correct me, if otherwise).

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.29. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

It looks like #3824 will address most of these issues!

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[npolshakova]

Hi @danwinship, just checking in once more as we approach the 1.29 enhancement freeze deadline this week on 01:00 UTC, Friday, 6th October, 2023. The status of this enhancement is marked as at risk for enhancement freeze.

It looks like #3824 will address the outstanding issues. Let me know if I missed anything. Thanks!

[danwinship]

@npolshakova #3824 is merged now... is this close enough or do I need to file an exception?

[npolshakova]

@danwinship, yep since there was a verbal approval on #3824, you do not need to file an exception. Now that it's merged you are tracked for enhancement freeze 🚀 .

[harshitasao]

Hi @danwinship 👋, v1.29 Docs Shadow here
Does this enhancement work planned for v1.29 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.29 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, 19 October 2023.
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

[harshitasao]

Hi @danwinship! The deadline to open a placeholder PR against k/website for required documentation is Thursday, 19 October. Could you please update me on the status of docs for this enhancement?
Thank you!

[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

[danwinship]

/remove-lifecycle rotten
/label lead-opted-in
/milestone v1.33

targeting GA for 1.33

[ArkaSaha30]

Hello @danwinship 👋, v1.33 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025.

This enhancement is targeting stage stable for v1.33 (correct me, if otherwise)
/stage stable

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v.133. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria.
• KEP has submitted a production readiness review request for approval and has a reviewer assigned.
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here)

For this KEP, we would just need to update the following:

• Looks like everything is in place, only the PR needs to be merged and we will be good to Track for Enhancements Freeze

The status of this enhancement for now is marked as At risk for enhancements freeze.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[bridgetkromhout]

Looks like everything is in place, only the #5044 needs to be merged and we will be good to Track for Enhancements Freeze

@ArkaSaha30 The PR linked above is merged, so I think we can move this from "At risk" to "Tracked".

[ArkaSaha30]

Awesome! This enhancement is now marked as Tracked for enhancements freeze

[ArvindParekh]

Hello, @danwinship 👋, v1.33 Docs Shadow here.

Does this enhancement work planned for v1.33 require any new docs or modifications to existing docs?

If so, please follow the steps here to open a PR against the dev-1.33 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 27th February 2025 18:00 PDT.

Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

[danwinship]

@ArvindParekh there is already a docs PR for 1.33, kubernetes/website#49453 (which needs review; I had a few questions). There is also a blog post scheduled for Feb 28.

[Udi-Hofesh]

Hey @danwinship 👋 -- this is Udi (@Udi-Hofesh) from the 1.33 Communications Team!

For the 1.33 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!

As you may be aware, feature blogs are a great way to communicate to users about features that fall into (but are not limited to) the following categories:

• This introduces some breaking change(s)
• This has significant impacts and/or implications to users
• ...Or this is a long-awaited feature, which would go a long way to cover the journey more in detail 🎉

To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Wednesday, 5th March, 2025? For more information about writing a blog, please find the blog contribution guidelines 📚

Tip

Some timelines to keep in mind:

• 02:00 UTC Wednesday, 5th March, 2025: Feature blog PR freeze
• Monday, 7th April, 2025: Feature blogs ready for review
• You can find more in the release document

Note

In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[danwinship]

Blog post already went out yesterday, "NFTables mode for kube-proxy". 🙂

[aojea]

Blog post already went out yesterday, "NFTables mode for kube-proxy". 🙂

Awesome, congratulations

[ArkaSaha30]

Hello @danwinship 👋, v1.33 Enhancements team here.

With all the implementation (code-related) PRs merged per the issue description:

• KEP-3866 nftables kube-proxy to GA kubernetes#129653

This enhancement is now marked as Tracked for code freeze for the {current release} Code Freeze!

Additionally, please let me know if there are any other PRs in k/k that we should track for this KEP, so that we can maintain accurate status.

Please note that KEPs targeting stable need to have the status field marked as implemented in the kep.yaml file after code PRs are merged and the feature gates are removed.

[Udi-Hofesh]

Blog post already went out yesterday, "NFTables mode for kube-proxy". 🙂

Awesome thank you!