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

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

    XMLWordPrintable

Details

    • CMO routes optional
    • False
    • None
    • False
    • Not Selected
    • NEW
    • To Do
    • MON-3152Optional built-in monitoring
    • NEW
    • 80
    • 80% 80%
    • 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.

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

       

       

       

       

      Attachments

        Issue Links

          relates to

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OBSDA-242 Make Cluster Monitoring Operator optional

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • To Do

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OBSDA-278 Don't block Cluster Monitoring Operator if Routes aren't accepted

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • In Progress
          links to

          GitHub openshift/cluster-monitoring-operator#1885: MON-2951: create Routes only with ingress operator

          Activity

            People

              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

              Dates

                Created:
                Updated:
                Resolved: