Goal

We need to explore how we can use the console public URL for the shared ingress in the 4.9 tech preview. The current POC uses the ACM URL, but 4.9 this will need to be the OCP console public URL.

Will this ingress be created by the console operator or the ACM operator?

There is a fair amount of custom logic for creating the ingress. If the console operator creates the ingress, it would have to implement that logic.

If the ACM operator continues to create the ingress, it will need to honor the custom route settings from https://github.com/openshift/enhancements/pull/577 and the legacy console operator config. The console operator would also need to skip creating its route.

We need to understand the impact to backwards compatibility as well since the ACM operator supports previous OpenShift versions. We should only have the consoles under a single URL if the feature gate from CONSOLE-2845 is enabled.

Acceptance Criteria

• Work with the ACM team to explore the which operator will create the shared ingress
• Identify any issues that could break ACM operator compatiblity with older OpenShift versions
• Identify other blockers or concerns
• Document the recommendation

Non-Goals

This is an R&D story only. This story does not cover any implementation.

cc showeimer jtalton rh-ee-jonjacks jhadvig@redhat.com