-
Bug
-
Resolution: Unresolved
-
Critical
-
4.14
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
MON Sprint 263, MON Sprint 264, MON Sprint 265, MON Sprint 266, MON Sprint 267, MON Sprint 268, MON Sprint 269, MON Sprint 270, MON Sprint 271, MON Sprint 272, Mon Sprint 273
-
11
-
Customer Escalated, Customer Facing, Customer Reported
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
remote_write - tokenURL not using proxy settings
Version-Release number of selected component (if applicable):
How reproducible:
Seen on a CU call - I will try to replicate in a azure lab
Steps to Reproduce:
configure remote_write with proxyurl and tokenURL
remoteWrite:
- url: https://test.azure.ingestion.com
oauth2:
clientId:
secret:
name: azure-monitor
key: id
clientSecret:
name: azure-monitor
key: secret
tokenUrl: https://login.microsoftonline.com/oauth2/v2.0/token
.....
queueConfig:
maxSamplesPerSend: 2000
capacity: 10000
maxShards: 40
proxyUrl: http://proxy.fisdev.local:8080
Observe timeouts in the logs against the token URL
Post \"https://login.microsoftonline.com/xxx/oauth2/v2.0/token\": dial tcp 20.190.157.12:443: connect: connection timed out"
test curling the remote_write endpoints from within the prometheus pods.
Observe that curls via the proxy to the tokenURL work..but do not without the proxy - timing out - the same result as the error seen in the logs
Actual results:
Remote_write fails with connect: connection timed out"
Expected results:
TokenURL is proxied
Additional info:
- blocks
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- is related to
-
RFE-6897 Expose remoteWrite.azureAD in cluster-monitoring-config
-
- Refinement
-
- links to
