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

Prevent creating more than one instance of IstioCNI

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • OSSM 3.0-TP1
    • None
    • Project Sail
    • None

      When you create two instances of IstioCNI, one of two things can happen:

      • if both instances use the same namespace, then the controller falls into an infinite loop
      • if two different namespaces are used, the second IstioCNI reconciliation will fail because it won't be able to create the istio-cni ClusterRole, since it will already exist

      For now, IstioCNI must be a singleton. To achieve this, we should ensure that the IstioCNI name is always "default".

            mluksa@redhat.com Marko Luksa
            mluksa@redhat.com Marko Luksa
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: