Hi Dirk,
As far as I know, the menu doesn't come from the Manage pods. It comes from MAS core.
The navigation, the login and the API calls are served by the core routes, each on its own hostname under your MAS domain. When the browser loads Manage from your new public name, it still calls those core hostnames. They only resolve to the NLB in your private subnet, so from the internet they fail, and you get the Manage page without its frame.
So one extra route won't be enough. Here's what I'd try:
- Publish the MAS domain itself through the public ALB, same hostnames, with split DNS. In Route 53, the public hosted zone points to the ALB and the private one keeps pointing to the NLB. MAS keeps generating the URLs it already knows, so redirects and the menu work.
- Keep MEA closed with an ALB or WAF rule on the MEA host or path. That's cleaner than keeping it private by simply not publishing it.
- Not sure which hostnames you need? Run
oc get routes -n mas-<instance>-core, then the same on mas-<instance>-manage.
One last thing. There's a recent thread here on MAS 9.2 and path-based routing instead of subdomains. If 9.2 is on your roadmap, it'd make the ALB part much simpler. Worth a look.
Khalil