We don't do anything to disable the default console route when the console hostname is customized. The problem is that users who visit the default route will not be able to login since the OAuth callback will use the public URL, and the state cookie will be missing. We should provide a redirect to the correct public URL from the previous, default route (ideally preserving the path and any query parameters). This will allow old bookmarks and links to keep working.
I see 2 options initially: 1. - we delete the default route. - if the custom route is removed, we hope we get the default back. - we go degraded if we cannot due to a squatter. 2. - we find a base image in our registry with node.js or python - we write a small node.js or python script that acts as a redirect server. we would do similar to the downloads server by injecting our script with the inline YAML (little gross) - we pass the custom-URL into the image as an env var or config map - we create a pod with that image called 'default-route-redirect' in 'openshift-console' and deploy it Either seems a reasonable solution, but the second is a better experience, we will just have a small stack of hacks to maintain. The first leaves the admin with more to fix later if something steals our route. I can't think of a good reason for a squatter to want console-openshift-console. off the top of my head.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409