Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-38655

Proxy URL NOT injected in UWM Prometheus after configuring remote-write

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.18.0
    • 4.16.z
    • Monitoring
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • No
    • None
    • None
    • MON Sprint 260, MON Sprint 261, MON Sprint 262
    • 3
    • Done
    • Bug Fix
    • Hide

      Previously, the Prometheus remote-write proxy configuration was not correctly applied to the Prometheus user workload custom resource (CR), which caused communication and data collection problems in the cluster. With this release, the user workload monitoring (UWM) Prometheus configurations, including user workload Prometheus, correctly inherit the proxy settings from the cluster proxy resource. (OCPBUGS-38655)
      ====
      Previously, the cluster-wide Proxy wasn't taken into account while configuring proxying for the UWM Prometheus remote write endpoints. With this release, CMO will take cluster-wide Proxy into account.
      Show
      Previously, the Prometheus remote-write proxy configuration was not correctly applied to the Prometheus user workload custom resource (CR), which caused communication and data collection problems in the cluster. With this release, the user workload monitoring (UWM) Prometheus configurations, including user workload Prometheus, correctly inherit the proxy settings from the cluster proxy resource. ( OCPBUGS-38655 ) ==== Previously, the cluster-wide Proxy wasn't taken into account while configuring proxying for the UWM Prometheus remote write endpoints. With this release, CMO will take cluster-wide Proxy into account.
    • None
    • None
    • None
    • None

      Description of problem:

      After configuring remote-write for UWM prometheus named "user-workload" in configmap named user-workload-monitoring-config, the proxyURL (same as cluster proxy resource) is not getting injected at all.

      Version-Release number of selected component (if applicable):

      4.16.4

      How reproducible:

      100%

      Steps to Reproduce:

      1. Configure proxy custom resource in RHOCP 4.16.4 cluster
2. Create user-workload-monitoring-config configmap in openshift-monitoring project
3. Inject remote-write config (without specifically configuring proxy for remote-write)
4. After saving the modification in  user-workload-monitoring-config configmap, check the remoteWrite config in Prometheus user-workload CR. Now it does NOT contain the proxyUrl. Example snippet:
==============
apiVersion: monitoring.coreos.com/v1
kind: Prometheus
metadata:
[...]
  name: user-workload
  namespace: openshift-user-workload-monitoring
spec:
[...]
  remoteWrite:
  - url: http://test-remotewrite.test.svc.cluster.local:9090    <<== No Proxy URL Injected

      Actual results:

      UWM prometheus CR named "user-workload" doesn't inherit the proxyURL from cluster proxy resource.

      Expected results:

      UWM prometheus CR named "user-workload" should inherit proxyURL from cluster proxy resource and it should also respect noProxy which is configured in cluster proxy.

      Additional info:

              rh-ee-amrini Ayoub Mrini
              rhn-support-dgautam Dhruv Gautam
              None
              Simon Pasquier
              Junqi Zhao Junqi Zhao
              None
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: