-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.16.z
-
None
-
Moderate
-
No
-
MON Sprint 260, MON Sprint 261, MON Sprint 262
-
3
-
False
-
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:
- is related to
-
OCPBUGS-42413 proxyUrl is not injected to UWM prometheus CR while the remoteWrite.url is not in the noProxy list
- Closed
- relates to
-
OCPBUGS-38289 [CEE.neXT]noProxy URL not available in Prometheus k8s CR after configuring remote-write
- Verified
- links to