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

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

XMLWordPrintable

    • CMO routes optional
    • False
    • None
    • False
    • Not Selected
    • NEW
    • To Do
    • MON-3152Optional built-in monitoring
    • NEW
    • 20% To Do, 0% In Progress, 80% Done
    • 0

      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.

      • Alertmanager (main)
      • Prometheus k8s (API)
      • Prometheus k8s (federation)
      • Prometheus UWM (federation)
      • Thanos Querier
      • Thanos Ruler (UWM)

       

       

       

       

            jfajersk@redhat.com Jan Fajerski
            wgordon.openshift Will Gordon
            Tai Gao Tai Gao
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: