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

noProxy URL not available in Prometheus k8s CR after configuring remote-write

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • None
    • 4.16.z
    • Monitoring
    • ?
    • Important
    • None
    • MON Sprint 258
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, the "noProxy" field from the cluster-wide Proxy wasn't taken into account while configuring proxying for the Platform Prometheus remote write endpoints. With this release, CMO will no longer configure proxying for any remote write endpoint whose URL should bypass proxy according to "noProxy".
      Show
      Previously, the "noProxy" field from the cluster-wide Proxy wasn't taken into account while configuring proxying for the Platform Prometheus remote write endpoints. With this release, CMO will no longer configure proxying for any remote write endpoint whose URL should bypass proxy according to "noProxy".
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-39029. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-38289. The following is the description of the original issue:

      Description of problem:

      The cluster-wide proxy is getting injected for remote-write config automatically but not the noProxy URLs in Prometheus k8s CR which is available in openshift-monitoring project which is expected. However, if the remote-write endpoint is in noProxy region, then metrics are not transferred.

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

      RHOCP 4.16.4

      How reproducible:

      100%

      Steps to Reproduce:

      1. Configure proxy custom resource in RHOCP 4.16.4 cluster
      2. Create cluster-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  cluster-monitoring-config configmap, check the remoteWrite config in Prometheus k8s CR. Now it contains the proxyUrl but NOT the noProxy URL(referenced from cluster proxy). Example snippet:
      ==============
      apiVersion: monitoring.coreos.com/v1
      kind: Prometheus
      metadata:
      [...]
        name: k8s
        namespace: openshift-monitoring
      spec:
      [...]
        remoteWrite:
        - proxyUrl: http://proxy.abc.com:8080     <<<<<====== Injected Automatically but there is no noProxy URL.
          url: http://test-remotewrite.test.svc.cluster.local:9090
          

      Actual results:

      The proxy URL from proxy CR is getting injected in Prometheus k8s CR automatically when configuring remoteWrite but it doesn't have noProxy inherited from cluster proxy resource.

      Expected results:

      The noProxy URL should get injected in Prometheus k8s CR as well.

      Additional info:

       

              rh-ee-amrini Ayoub Mrini
              openshift-crt-jira-prow OpenShift Prow Bot
              Junqi Zhao Junqi Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: