-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
3
-
False
-
None
-
False
-
OCPSTRAT-440 - OpenShift Eng should be the first to know if OCP code doesn't work in managed services
-
-
-
OTA 236
We need to create the OHSS ticket [1] to create a DNS entry for the OSUS route (similar to the current stage cluster), so that a defined route (for OSUS) can exist for the integration cluster with the EC builds. The route is an envoy configuration [2]. It should be similar to the Cincinnati stage setup
# Cluster for the `upgrades_info` service: - name: upgrades_info connect_timeout: 2s type: STRICT_DNS lb_policy: ROUND_ROBIN load_assignment: cluster_name: upgrades_info endpoints: - lb_endpoints: - endpoint: address: socket_address: address: cc533os557xkwku.api.stage.openshift.com port_value: 443 transport_socket: name: envoy.transport_sockets.tls typed_config: "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext common_tls_context: validation_context: trusted_ca: filename: /etc/ssl/certs/ca-certificates.crt
[1]https://issues.redhat.com/projects/OHSS/issues/
Definition of done:
- Create OHSS ticket to for creating DNS entry for the OSUS route running in integration environment (similar to the current stage cluster).
- Create route for the OSUS running in the integration environment (refer https://gitlab.cee.redhat.com/service/app-interface/-/blob/master/docs/app-sre/sop/add-route-for-ocm-component.md)
- Add required envoy config changes in app-interface gitlab
- mentioned on
(3 mentioned on)