-
Story
-
Resolution: Done
-
Undefined
-
None
-
1
-
False
-
None
-
False
-
ACM-8664 - Expanded proxy scenarios between hub and managed cluster
-
-
-
RHOBS Sprint 20, MCO Sprint 20, MCO Sprint 21, MCO Sprint 24
-
No
The proposed solution for this problem is to use the `AddOnDeploymentConfig`'s customized variables to allow a custom base URL for the Observatorium API and Alertmanager Routes to be passed all the way down to the metrics-collector/managed cluster.
We will need to test whether a SAN has to be added to the server (obs api) certificate with the FQDN of the intermediate component.
Ensure updates in the base URL are gracefully handled.
Note: we cannot support TLS termination because the metrics-collector uses MTLS to authenticate with the Observatorium API.
- blocks
-
ACM-12275 Automate creation of proxy routes for custom observability and alertmanager URL
- New
- depends on
-
ACM-12191 Observability - alertmanager configuration with load balance proxy tls passthrough
- Closed
-
ACM-12271 Observability - metrics configuration with load balance proxy tls passthrough
- Closed
- is documented by
-
ACM-11407 [Obs Tech preview] Document how to configure a custom url for the Observability Hub API and alertmanager
- Closed