Uploaded image for project: 'Connectivity Link'
  1. Connectivity Link
  2. CONNLINK-669

Improve handling of missing Service Mesh

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • RHCL Operator
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      When installing Connectivity Link today, if Service Mesh is not yet installed on the cluster and the user creates the Kuadrant object, it goes into a failing state.  However, once Service Mesh is installed, users must manually restart the operator pod in order to allow the operator to attempt to setup the Kuadrant object.

      This is not very GitOps friendly and it also does not adhere to k8s standards as an eventually consistent system.

      It would be great if Connectivity Link were able to automatically detect once Service Mesh is installed and attempt to resolve the issue, or simply periodically attempt to reconcile the changes if it is an failed state.

              Unassigned Unassigned
              troyer@redhat.com Trevor Royer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: