Uploaded image for project: 'OpenShift Windows Containers'
  1. OpenShift Windows Containers
  2. WINC-882

Separate CNI configuration from kube-proxy service definition

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • None
    • None
    • 5
    • False
    • None
    • False

      Description

      The CNI configuration and HNS endpoint creation have been squashed into one script. This was done in order to work around WICD's ability to only run powershell scripts before a service is started.

      Engineering Details

      • The WICD API may have to adjusted in order to accomplish this, either by adding the ability to run powershell after a service is confirmed started, or as a separate 'service' all together.

      Acceptance Criteria

      • CNI configuration is done separately and independently of the kube-proxy service configuration

              Unassigned Unassigned
              rh-ee-ssoto Sebastian Soto
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: