-
Bug
-
Resolution: Unresolved
-
Critical
-
4.14
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
In Progress
-
Enhancement
-
allow using remoteWrite[].oauth2.proxyFromEnvironment for cluster-wide proxy for 4.18.z, this feature is implemented in 4.19 and later builds
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-63409. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-63408. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-45671. The following is the description of the original issue:
—
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:
- clones
-
-
- Verified
-
- is blocked by
-
-
- Verified
-
- links to
