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

Make Cluster Monitoring Operator optional

    XMLWordPrintable

Details

    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%
    • 0

    Description

      Epic Goal

      • Make it possible for customers to disable the Cluster Monitoring operator by leveraging the OCPPLAN-9638 Composable OpenShift capability.

      Note: MON-3152 tracks the individual workstreams.

      Why is this important?

      • For Managed OpenShift on AWS (ROSA) with HyperShift, we get metrics from the control plane, so we don't need the cluster monitoring capabilities.
      • Customers with existing / preferred monitoring solutions want to have as small of an OpenShift resource footprint as possible.

      Scenarios

      1. This feature must consider the different deployment footprints including self-managed and managed OpenShift, connected vs. disconnected (restricted and air-gapped), implications for auto scaling, chargeback/showback use scenarios, etc.
      2. Disabled configuration must persist throughout cluster lifecycle including upgrades.

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. …

      Open questions::

      1. …

      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>

      Attachments

        Issue Links

          is blocked by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OCPNODE-708 Tech preview of KEDA

          • 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.
          • Closed

          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-248 Replace prometheus-adapter by metrics-server

          • 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
          is incorporated by

          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. OCPSTRAT-1308 OpenShift Optional Capabilities (Phase 7)

          • Critical - To be worked on immediately following BLOCKER issues.
          • New

          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. OCPSTRAT-731 OpenShift Optional Capabilities (Phase 6)

          • Critical - To be worked on immediately following BLOCKER issues.
          • In Progress

          Initiative - A large product/portfolio goal or focus area that has clear start and completion criteria MON-3152 Optional built-in monitoring

          • 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

          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. OCPSTRAT-36 OpenShift Optional Capabilities (Phase 4)

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          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. OCPSTRAT-421 OpenShift Optional Capabilities (Phase 5)

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          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. OCPSTRAT-147 OpenShift Optional Capabilities (Phase 3)

          • 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.
          • Closed
          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MON-2965 Deploy the monitoring console plugin resources via CMO

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Release Pending

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MON-2951 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.
          • Closed
          links to

          GitHub crc-org/snc#614: Add capabilities for 4.12

          GitHub openshift/cluster-monitoring-operator#2000: OpenTelemetry Support

          GitHub openshift/enhancements#1280: Proposal for an operator health metric

          Activity

            People

              rh-ee-rfloren Roger Florén
              julim Ju Lim
              Adel Zaalouk, Ben Parees, Daniel Mohr, Jan Fajerski, Jeremy Eder, Ju Lim, Simon Pasquier, Will Gordon
              Junqi Zhao Junqi Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              28 Start watching this issue

              Dates

                Created:
                Updated: