Uploaded image for project: 'OpenShift Top Level Product Strategy'
  1. OpenShift Top Level Product Strategy
  2. OCPPLAN-7691

Enable 3rd party network plugins for Windows Containers in OpenShift

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • False
    • False
    • ?
    • No
    • ?
    • ?
    • ?
    • Undefined

      Enable 3rd party network plugins for Windows Containers in OpenShift

      Background

      **Here are the list of certified network plugins we support in OpenShift: https://coreos.slack.com/files/U0106SRU72R/F01R7LT31EJ/openshift_3rd-party_sdn_vendor_kubernetes_cni_plug-ins?origin_team=T027F3GAJ&origin_channel=Psearch

      But as adoption of Windows grows, customers are asking for more 3rd party plugins to be supported for their Windows nodes in OpenShift - particularly Calico, Cisco ACI etc.

      This feature comprises of 3 parts

      1. WINC-660: Decouple OVNHybrid from WMCO as the default network option so customers can chose a different plugin
      2. WINC-619: Validate important 3rd party network plugins including Calico and NSX 3.0. This step need not be automated and can be completed manually. Refer to steps Add Windows nodes to the cluster 
        and below in this doc: https://docs.projectcalico.org/getting-started/windows-calico/openshift/installation
      3. WINC-656: After Calico has been enabled, work with Tigera to test that their network policies work correctly. We'll try to get this work prioritized by the partner. Sample network policies: https://docs.projectcalico.org/security/calico-network-policy 

              Unassigned Unassigned
              anachand Anandnatraj Chandramohan (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: