virubiotor
commented
2 months ago @CESARDELATORRE Right now the code from the control-plane-ui-service uses the same protocol and IP that the control-plane-app and the 88 port
function useAlertsDashboardUri() {
const [alertsUiUri, setAlertsUiUri] = useState('');
useEffect(() => {
const newUri = `${window.location.protocol}//${window.location.hostname}:88`;
setAlertsUiUri(newUri);
}, []);
return alertsUiUri;
}Previously (~3 months ago), it used to be an env variable with the address of the Alerts-UI service. I feel like this might be the change you are mentioning.
This change was made in this commit: https://github.com/Azure/mec-app-solution-accelerator/commit/f7c60f5797711c20e8575479c6e6528ef9031baa
Related issue: https://github.com/Azure/mec-app-solution-accelerator/issues/117#issuecomment-1954921164
Should we rollback this changes and use the Cluster IP as an environment variable that must be set by the user? How should this be managed in the deployment script?
CESARDELATORRE
[P0] [BUG] Link en Control Plan app to Alerts-UI has wrong PORT
The root cause can be that it's using a different IP address, why? Previously, we were using the same IP address for all the services (the real IP of the machine) and then we just use different ports for the app. THat's the way it needs to be so we can also access the app from remote machines. We need to use the real machine's IP.
It goes to: http://192.168.0.6:88/ --> Tha's not the IP
It should be, if I check the URL in K8s Dashboard: http://192.168.0.4:88/
In the K8s dashboard services I see it like this:
Basically the link needs to find out the IP and port dynamically....
BUT MOST IMPORTANTLY, IT HAS TO USE THEREAL IP OF THE MACHINE, so you can access remotely easier.
Previosly (v 1.8) I think we were using the same IP for all the public services in K8s, as you can see here, the IP 172.30.1.75 for all the public services. But that's not the way I see it in v1.9 with Aio...: