[Bug] Websocket not working with Cryostat exposed on a specific Path

[ElfoLiNk]

Current Behavior

I'm trying to run Crystat under a path prefix inside kubernetes like hostname.com/cryostat.

To make the javascript load I had to use the 2.4.1-SNAPSHOT version but the websocket it's trying to call the API under the root /

Expected Behavior

Websocket should use correct endpoint when cryostat is exposed via an ingress under a subpath other than root /

Steps To Reproduce

No response

Environment

- Environment: AKS 1.27
- Version: 2.4.1-snapshot

Anything else?

No response

[andrewazores]

I think this is a duplicate of #1810 , though that bug "should" be fixed in the latest 2.4.1-snapshot images...

Sounds like the relative path is working properly for the JavaScript loading and perhaps API calls, but not for the Websocket path.

[andrewazores]

The more I'm digging into this the more I'm finding bits and pieces that would need patching to take into account that the API paths may not be mounted on the root path. I'm not sure I will be able to prioritize work on this in the near term since we are only planning a 2.4.1 bugfix release from this codebase, and after that will be 3.0 which is a substantial rewrite and rearchitecture under the covers. From some preliminary testing I think what you're looking to achieve is already possible with 3.0, but there are a lot of other features missing so far to get that up to speed.