-
Notifications
You must be signed in to change notification settings - Fork 46
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
Host Process containers for CNIs #217
Comments
/good-first-issue ping me, @knabben , @dougsland for help getting started |
@jayunit100: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
We should try and target the new out-of-tree windows-service-proxy / kube-proxy with this work too. |
This is supported in Antrea v1.10 as well: look for cc @jayunit100 |
@antoninbas .. can we run OVS in the pod or that still has to be standalonE? |
Wenying has commented on the Antrea Slack that OVS cannot be run as a container yet. |
see https://github.com/kubernetes-sigs/sig-windows-tools/pull/239/files
And lets co-evolve to accomodate flannel and calico host-process CNIs.
calico: https://projectcalico.docs.tigera.io/getting-started/windows-calico/quickstart#install-calico-for-windows-using-hostprocess-containers
antrea: https://antrea.io/docs/v1.10.0/docs/windows/
some links for noobs that might help
The text was updated successfully, but these errors were encountered: