Uploaded image for project: 'Observability and Data Analysis Program'
  1. Observability and Data Analysis Program
  2. OBSDA-278

Don't block Cluster Monitoring Operator if Routes aren't accepted

    XMLWordPrintable

Details

    • Feature
    • Resolution: Unresolved
    • Major
    • None
    • None
    • PM Monitoring
    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%
    • 0

    Description

      Proposed title of this feature request

      In a world without an IngressController (see RFE-3395), we should still ensure that the Cluster Monitoring Operator and stack can become available without waiting on Routers to be accepted

      Why does the customer need this? (List the business requirements)

      The Ingress Controller needs to be optional (see RFE-3395) and we want to still ensure that CMO becomes available without an Ingress Controller

      List any affected packages or components.

      Alertmanaged and Thanos (https://redhat-internal.slack.com/archives/C02LM9FABFW/p1674676800930739?thread_ts=1674676707.511489&cid=C02LM9FABFW)

      Attachments

        Issue Links

          Activity

            People

              rh-ee-rfloren Roger Florén
              wgordon.openshift Will Gordon
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: