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

Move OSSM3 Operator to istio-ecosystem

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Blocker Blocker
    • OSSM 3.0-TP1
    • None
    • Sail Operator
    • None
    • Move operator to upstream
    • False
    • Hide

      None

      Show
      None
    • False
    • Done
    • 0% To Do, 0% In Progress, 100% Done

      My understanding from the last TOC meeting is that we had approval to move the "Sail Operator" to the istio-ecosytem organization. This issue is to cover that work.

      With the operator being moved to the istio-ecosystem org, we should also look to purge any uses of the "Maistra" name that exist (including branches).

      The new name should ideally be "Istio Operator", though if that's unacceptable due to concerns of confusion with the IstioOperator CRD we could consider adding another differentiating term like "Istio OLM Operator" or similar.

      Of course, longer term, it'd be nice if we did influence the deprecation of the IstioOperator CRD and more clarity on how to configure Istio...but that would be a longer term goal (This is not part of this story, though it was discussed by John Howard in the TOC call).

              jsantana@redhat.com Jonh Wendell
              jlongmui@redhat.com Jamie Longmuir
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: