Allow HostNetwork Pods to Use User Namespaces

[HirazawaUi]

Enhancement Description

• One-line enhancement description (can be used as a release note): Allow pods to use user namespaces and hostNetwork simultaneously
• Kubernetes Enhancement Proposal:
• Discussion Link: https://kubernetes.slack.com/archives/C0BP8PW9G/p1759422276851019
• PRs by stage and milestone:
  • Alpha - v1.35
    • KEP (k/enhancements) update PR(s): KEP-5607: Allow hostNetwork pods to use user namespaces #5608
    • Code (k/k) update PR(s): KEP-5607: Allow hostNetwork pods to use user namespace kubernetes#134893
    • Docs (k/website) update PR(s): kep-5607: Add docs for UserNamespacesHostNetworkSupport feature gate  website#52875
  • Alpha - v1.36
    • KEP (k/enhancements) update PR(s): KEP-5607: Add implementation content for v1.36 #5745
    • Code (k/k) update PR(s): Kubelet: Add alpha-2 stage implementation for UserNamespacesHostNetworkSupport feature gate kubernetes#135828
    • Docs (k/website) update PR(s): WIP: Add documentation for KEP-5607 in v1.36 website#54664

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

[HirazawaUi]

/sig node

[HirazawaUi]

@haircommander @SergeyKanzhelev

Although there are only 5 days left until the PRR freeze, but I went ahead and completed this KEP. Given its straightforward code implementation, I think there are may no blocking issues for us to advance this feature in v1.35.

If you agree with this proposal, please add the lead-opted-in label to this issue. If you consider the timeline too tight, please disregard this comment and I will advance this feature in v1.36 instead.

[SergeyKanzhelev]

/milestone v1.35
/label lead-opted-in

I am fine tracking it for 1.35. Just make sure you are not overloaded with KEPs

/assign @HirazawaUi

[aibarbetta]

Hello @HirazawaUi 👋, v1.35 Enhancements team here.

This is a reminder of the upcoming PRR freeze on Thursday 9th October 2025 (AoE) / Friday 10th October 2025, 12:00 UTC.

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

Here's where this enhancement currently stands:

• PR open or merged with the KEP's PRR questionnaire filled out.
• PR open or merged with kep.yaml updated with the stage, latest-milestone, and milestone struct filled out.
• PR open or merged with a PRR approval file with the PRR approver listed for the stage the KEP is targeting.

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

• Open a PR adding a PRR approval file

Note that the PRs are not required to be approved or merged by the PRR freeze deadline. Having the PRR questionnaire filled out by the deadline will help ensure that the PRR team has enough time to review your KEP before enhancements freeze on Thursday 16th October 2025 (AoE) / Friday 17th October 2025, 12:00 UTC. For more information on the PRR process, see here.

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

If you anticipate missing PRR freeze, you can file an exception request in advance.

Thank you!