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

Expose prometheus connection information in a secret

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • rhos-18.0.6
    • rhos-18.0.4
    • telemetry-operator
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • telemetry-operator-container-1.0.7-3
    • None
    • Hide
      .Prometheus connection information is exposed in a secret

      Telemetry Operator now creates a secret with the internal Prometheus connection details. Other OpenShift services can use that secret as a service discovery mechanism to connect to Prometheus.
      Show
      .Prometheus connection information is exposed in a secret Telemetry Operator now creates a secret with the internal Prometheus connection details. Other OpenShift services can use that secret as a service discovery mechanism to connect to Prometheus.
    • Enhancement
    • Done
    • CloudOps 2025 Sprint 2
    • 1
    • Moderate

      The watcher team needs to connect to prometheus. The connection information should be exposed inside a secret and then used by watcher, autoscaling and openstackclient to retrieve the connection information.

       

      The secret should certainly include the url, port and maybe a reference to a secret with CA certificate to be used would be useful.

              rhn-engineering-jlarriba Juan Larriba
              rh-ee-jwysogla Jaromir Wysoglad
              rhos-conplat-observability
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: