Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-5060

Improvements to CNI

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • Sail Operator
    • None
    • Improvements to CNI
    • False
    • None
    • False
    • To Do
    • 0% To Do, 50% In Progress, 50% Done
    • XL

      In OSSM 2.x, we had a custom istio-cni chart (and some CNI patches) that allowed us to install multiple DaemonSets in the cluster, one for each Istio version that is installed. With OSSM 3.0, we want to completely rely on upstream code and charts for CNI, which is why we need to find a solution to running/upgrading CNI for potentially diverging versions of Istio.

      Goals of this Epic include:

      • when we upgrade between minor versions, we must not break CNI

              dgrimm@redhat.com Daniel Grimm
              jsantana@redhat.com Jonh Wendell
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: