Business UI not loading

[planetf1]

When testing Egeria 3.11 odpi/egeria#6812 I was unable to get the business/polymer UI to work

I retested 3.10 and also had issues, so it's possibly I only tested the UI locally

• When deployed onto openshift, any connection to the nginx pod would immediately close the connection
• When deployed into rancher desktop, an attempt to to to / at nginx would result in a '404 page not found' being returned as a text error

It would appear that though nginx is working, the configured back-end for the root URL is behaving differently.

Note that the UI version (static) has not changed as per the issue above, but egeria itself is at 3.11, so the egeria UI application will be at a much later level

We need to do one of the following
a) Accept the UI (as deployed) is broken in the 3.11 charts - this would be unfortunate as I know some people want to use it, and it's going to be really useful/interesting as we converge the ui tech
b) Abandon/delay the 3.11 release (at least in full)- I do not think this is appropriate as it affects the core, and we have many more users using this . It also impacts upcoming conferences
c) Figure out a working config of the 'old' UI (would an old UI container working alongside current egeria chassis work?) - and implement in the charts
d) Have a working config of the new UI

This needs addressing imminently. the default action will unfortunately need to be a) due to schedule & upcoming conferences

Can you help @lpalashevski @sarbull @bogdan-sava ?

It's possible also the issue is caused by another change - like nginx version (we use a 'stable' image from the nginx team, published to aws), most likely it's due to UI chasis changes. Hopefully some rework in the charts to use an old UI chassis, or a config change in nginx for the URLs will address - and fuller changes can be made once the new UI is ready.

[planetf1]

More tests.

On rancher (local k8s) both 3.10 and 3.11 ARE working ok, with the GUI correctly appearing.

[planetf1]

Also ok on openshift. Issue appeared to be with the LoadBalancer service.

Closing as user error