Add xt_recent kernel module so that Kubernetes Services with Session Affinity work in WSL

[douglascamata]

Is your feature request related to a problem? Please describe.

The lack of this kernel module's presence makes Kubernetes Service with Session Affinity unusable and breaks a lot of things inside k8s clusters that could be running either inside the WSL VM directly or through containers inside the VM.

Describe the solution you'd like

I would like the xt_recent to be present by default so that I don't need to recompile the kernel myself to get Kubernetes Services to work with their basic feature set.

Describe alternatives you've considered

I tried recompiling the kernel myself, obviously. It's time consuming and annoying that I have to figure out what's broken, what I need to do, then finally do it. The investigation is not easy at all.

I can't patch literally all the services out there in k8s manifests, Helm charts, operators and so on to avoid using the client session affinity option.

Additional context

This is a revival of #7124, but as a feature request instead of a bug.

Would also love to see CONFIG_NETFILTER_XT_TARGET_CT=y and CONFIG_NETFILTER_XT_TARGET_TPROXY=y present so that things like Cilium could work inside WSL.

We already had open PRs to fix this issue, but they were not accepted without a good and clear explanation on why, as I noted on #7124 (comment).

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

• Missing xt_recent kernel module resulting in inability to run Kubernetes with Session Affinity (#7124), similarity score: 0.83

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[soredake]

@kelsey-steele Hi! I've seen that you've fixed #8302, can you look at this issue too, please?

[mkarrmann]

+1 that this is rather important. It's strange that such an important use case which can be addressed with a simple use case has gone unaddressed for so long. People have been manually compiling their kernels just to make this minor config change for years now. Is there any reason the team is uninterested in addressing this @craigloewen-msft ?