-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows hostnetwork alpha #112961
Windows hostnetwork alpha #112961
Conversation
@@ -233,6 +233,15 @@ func (m *kubeGenericRuntimeManager) generatePodSandboxWindowsConfig(pod *v1.Pod) | |||
SecurityContext: &runtimeapi.WindowsSandboxSecurityContext{}, | |||
} | |||
|
|||
if utilfeature.DefaultFeatureGate.Enabled(features.WindowsHostNetwork) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just curiosity, what is the relation with features.WindowsHostProcessContainers
?
are all WindowsHostProcessContainers
HostNetwork pods?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, All pods that contain HostProcessContainers must set hostNetwork=true
(this is enforced at API admission).
Really HostProcessContainers just start processes on the host but they are packages and deployed like contianers (hence the name).
With these changes pods that do not contain HostProcessContainers will have the option of using pod or node network namespace.
1a061eb
to
6393b15
Compare
Signed-off-by: Mark Rossetti <marosset@microsoft.com>
Signed-off-by: Mark Rossetti <marosset@microsoft.com>
6393b15
to
0d54b19
Compare
0d54b19
to
485b9e5
Compare
/milestone v1.26 |
I have changes mostly working end-to-end based on https://github.com/marosset/containerd/tree/windows-host-network-support so I think we can get this merged into K8s for v1.26! /assign @jsturtevant @mrunalp @jayunit100 |
…t + unit tests Signed-off-by: Mark Rossetti <marosset@microsoft.com>
485b9e5
to
f4305db
Compare
/assign @dchen1107 |
/retest |
This PR looks fine. Noting per the enhancement, we will need e2e tests, but you need the CRI changes merged from this PR to make that possible. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: derekwaynecarr, marosset The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Allows kubelet to specific if Windows pods should be joined to the node or pod network namespace for Windows pods
Which issue(s) this PR fixes:
Part of: kubernetes/enhancements#3503
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/sig windows node
/area kubelet