The objective of this request is to enable one option to host separate OCP web console in a nodes' secondary interface or eventually in a secondary ingresscontroller.

Currently, the console route can be customized as the documentation and the oauth route as well. The issue of both configurations is that this design does not create one redundant or separate option for the web console and authentication communication, but it moves the routes between ingresscontrollers. 

The central idea on this RFE is giving one OCP architecture to create more flexible infrastructures where the console and authentication are completely separate and resilient in failure events. This also solves scenarios where the OCP cluster needs one dedicated web console access for one nature and a second web console for a second nature due to very strict security requirements.

Considering the shared summary, the RFE-3651 seems to be one pre requisite for the current request.

Also, during the implementation of this, the assymetric traffic events should be reviewed in this case as the OCP components only have one default gateway. Network traffic strategies should be applied to ensure that the primary traffic should be replied in the primary access and the secondary traffic by the respective access.

A list of affected components:

• Ingress controller
• OCP console
• OCP authentication
• OCP Networking /OVN-Kubernetes
• Metallb operator