Uploaded image for project: 'OpenShift Monitoring'
  1. OpenShift Monitoring
  2. MON-3311

Rename downstream Obo to Cluster Observability Operator

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • Rename downstream ObO
    • False
    • None
    • False
    • Not Selected
    • NEW
    • To Do
    • NEW
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      • Rename the downstream name of ObO. We'll be using  Cluster Observability Operator instead. This is a change that goes in line with other OpenShift Operators such as CMO (Cluster Monitoring Operator) or CLO (Cluster Logging Operator).

      Why is this important?

      • This change is being proposed so the naming is more specific and goes in line with other Cluster Operators and distinguishes it from MCO (Multi Cluster Observability Operator) from ACM. 

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Images should be built with the new naming and available in Quay
      • CPaaS repo should be available as a part of that
      • Docs should be pointing out to the new naming

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              dmellado1@redhat.com Daniel Mellado Area
              dmellado1@redhat.com Daniel Mellado Area
              Hongyan Li Hongyan Li
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: