This is a clone of issue OCPBUGS-38398. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-38174. The following is the description of the original issue:
—
Description of problem:
The prometheus operator fails to reconcile when proxy settings like no_proxy are set in the Alertmanager configuration secret.
Version-Release number of selected component (if applicable):
4.15.z and later
How reproducible:
Always when AlertmanagerConfig is enabled
Steps to Reproduce:
1. Enable UWM with AlertmanagerConfig enableUserWorkload: true alertmanagerMain: enableUserAlertmanagerConfig: true 2. Edit the "alertmanager.yaml" key in the alertmanager-main secret (see attached configuration file) 3. Wait for a couple of minutes.
Actual results:
Monitoring ClusterOperator goes Degraded=True.
Expected results:
No error
Additional info:
The Prometheus operator logs show that it doesn't understand the proxy_from_environment field.
- blocks
-
OCPBUGS-38400 Cannot use new proxy settings in Alertmanager configuration
- Closed
- clones
-
OCPBUGS-38398 Cannot use new proxy settings in Alertmanager configuration
- Closed
- is blocked by
-
OCPBUGS-38398 Cannot use new proxy settings in Alertmanager configuration
- Closed
- is cloned by
-
OCPBUGS-38400 Cannot use new proxy settings in Alertmanager configuration
- Closed
- links to
-
RHBA-2024:6401 OpenShift Container Platform 4.16.z bug fix update