Ok, I was able to sort this out -- but it was tricky because it requires: • Building the console image and setting

BASE_URL

to hardcode the correct paths into index.html for all the links to webpack scripts -- i.e.

/flyte/console

• Making sure to set that same value at runtime on the container (if it's set to the default of

/console

the web app misbehaves) • Additionally setting

BASE_HREF

in the console container (otherwise the uris in the browser history are wrong, and reloading the page will fail) • Set the

ADMIN_API_URL

to point to the right place - like

<https://foo.com/flyte>

• Updating the ingress to add the subpath support... carefully. ◦ The console endpoints must remain intact - so requests from

/flyte/console

must go to

/flyte/console

in flyteconsole service ◦ The API endpoints must be rewritten by the ingress -- so requests to

/flyte/api/...

must be rewritten as

/api/...

for all the API endpoints This could be made a lot simpler... but I don't see a good way around setting all this configuration like this right now (primarily b/c the console build process uses static absolute paths rather than relative)

I've also found that the code here does not appear to be right as

/console

is hardcoded -- https://github.com/flyteorg/flyteconsole/blob/34edde1cb2c7df2f77da6f9fabdefbe2d89c6353/packages/common/src/routes/index.ts#L25 I'm going to fork / build from that fork to confirm

And here -- https://github.com/flyteorg/flyteconsole/blob/34edde1cb2c7df2f77da6f9fabdefbe2d89c[…]ckages/oss-console/src/components/Breadcrumbs/registry/index.ts