Uploaded image for project: 'Cluster Observability Operator'
  1. Cluster Observability Operator
  2. COO-862

introduce a new Go module for the COO API

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • operator
    • COO go api module
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • 100% (High)
    • 8
    • 0

      Proposed title of this feature request

      What is the nature and description of the request?

      We are introducing the Incident detection feature in the ACM as well. This means that the multicluster-observability-addon (MCOA) depends on the cluster-observability-operator (COO) and it would be better to depend only on the COO APIs and not the full operator. This is currently not possible and it's the main goal of this feature.

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

      I think it's not really customer facing, but the decoupling is improvement for the future.

      List any affected packages or components.

      COO codebase. Additionally the API should not depend on the controller-runtime.

              tremes1@redhat.com Tomas Remes
              tremes1@redhat.com Tomas Remes
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: