Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-2577

[STF] Migrate STO to support Grafana Operator v5

XMLWordPrintable

    • [STF] Migrate STO to support Grafana Operator v5
    • False
    • Hide

      None

      Show
      None
    • False
    • Committed
    • Committed
    • Proposed
    • Done
    • OSP-6870 - Allow installation of STF in restricted-network environments
    • service-telemetry-operator-container-5.0.4-3
    • Committed
    • Proposed
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      STF will now request Grafana, GrafanaDashboard, and GrafanaDatasource objects from Grafana Operator v5 (community) if installed on the OpenShift deployment hosting STF.

      Grafana Operator v4 is no longer developed upstream as of December 2023 and it is recommended that users of Grafana Operator migrate to v5.

      STF will still request objects from Grafana Operator v4 if the Custom Resource Definitions (CRDs) for Grafana Operator v5 are not available.

      The default route for accessing Grafana when using Grafana Operator v5 has changed. In STF 1.5.3 and earlier the default route was "grafana-route". The new default route for Grafana has been updated to match the format of other routes, and now includes the name of the STF instance created, which if following official documentation will be "default-grafana-route".

      ~~~

      Documentation Changes:

      6.1.1. Configuring Grafana to host the dashboard has been updated to install Grafana Operator v5 by default.
      Show
      STF will now request Grafana, GrafanaDashboard, and GrafanaDatasource objects from Grafana Operator v5 (community) if installed on the OpenShift deployment hosting STF. Grafana Operator v4 is no longer developed upstream as of December 2023 and it is recommended that users of Grafana Operator migrate to v5. STF will still request objects from Grafana Operator v4 if the Custom Resource Definitions (CRDs) for Grafana Operator v5 are not available. The default route for accessing Grafana when using Grafana Operator v5 has changed. In STF 1.5.3 and earlier the default route was "grafana-route". The new default route for Grafana has been updated to match the format of other routes, and now includes the name of the STF instance created, which if following official documentation will be "default-grafana-route". ~~~ Documentation Changes: 6.1.1. Configuring Grafana to host the dashboard has been updated to install Grafana Operator v5 by default.
    • Enhancement
    • Proposed
    • Deploy
    • Service Telemetry Framework

      Overview

      Implement in service-telemetry-operator the ability to request Grafana, GrafanaDashboard, and GrafanaDatasource resources from the community operator using the updated CRD from the v5 channel.

      As of December 22, 2023 the community Grafana operator will no longer receive updates. As part of the effort to implement disconnected support in STF, all related/dependent operators must support disconnected as well. The Grafana operator from the community CatalogSource has been implemented in such a way that disconnected installation should be possible.

      Product Requirements

      • Will require a migration procedure for existing installations of STF that use the v4 channel of Grafana Operator.
      • Will require documentation updates to install Grafana Operator at the cluster-scope level using the v5 channel.
      • Will require functional testing repository updates.
      • Will require changes to service-telemetry-operator to support both v4 and v5 style installations of Grafana Operator
      • Will require re-testing of RBAC based controls with possible updates required

      Related Information

              lmadsen@redhat.com Leif Madsen
              lmadsen@redhat.com Leif Madsen
              Alex Yefimov
              rhos-dfg-cloudops
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: