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

Telemetry Operator does not create NetworkAttachment for Prometheus

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • rhos-18.0.6
    • rhos-18.0.3
    • telemetry-operator
    • None
    • CloudOps 2024 Sprint 23, CloudOps 2024 Sprint 24, CloudOps 2024 Sprint 25, CloudOps 2024 Sprint 26, CloudOps 2024 Sprint 27, CloudOps 2025 Sprint 1, CloudOps 2025 Sprint 2, CloudOps 2025 Sprint 5
    • 8
    • Important

      The way that isolated networks work is that they only give access to pods via an explicit NetworkAttachment (see Cinder with Storage network).

      The Prometheus pod needs to access the node_exporters ports in the compute nodes. This works fine when using install_yamls or cifmw because, apparently, both of them do "networking magic" (aka connect the ctlplane to the OCP general general via a router), but it would fail in case of isolated networks.

      Has been reported that following the deployment doc[1] to install the cluster by hand (like a user would do), the Prometheus is not able to connect to the node_exporters via ctlplane network.

      [1] https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/deploying_red_hat_openstack_services_on_openshift/index

       

              rhn-engineering-vimartin Victoria Martinez de la Cruz
              rhn-engineering-jlarriba Juan Larriba
              Leonid Natapov Leonid Natapov
              rhos-conplat-observability
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: