The ambassador's EXTERNAL-IP can’t be reached (minikube cluster)

[pribadihcr]

Hi
I tried the tutorial here: https://github.com/datarevenue-berlin/OpenMLOps/blob/master/tutorials/set-up-minikube-cluster.md

Look like there is no this service http://[EXTERNAL_IP_OF_JUPYTER_HUB_PROXY_PUBLIC]:80

Here my load balancers:
ambassador ambassador LoadBalancer 10.105.12.93 10.105.12.93 80:32714/TCP,443:32385/TCP 5h20m
mlflow mlflow LoadBalancer 10.96.12.12 10.96.12.12 5000:32132/TCP 3h11m
prefect prefect-server-ui LoadBalancer 10.105.217.102 10.105.217.102 8080:31497/TCP 3h4m

mlflow and prefect services can be accessed. But the ambassador's EXTERNAL-IP can’t be reached.

Thanks

[luckyluks]

Is there any update, comment or idea on this? maybe @bernardolk?

Unfortunately, I don't have any experience with Ambassador and how to debug it.
On my test setup with minikube, the Pods and Services are running. MLflow and Prefect are reachable via http://<minikube-IP>:<serivce-load-balancer-port>, but the ambassador external IP/Port refuses the connection. In addition, requests on addresses like http://mlflow.myambassador.com/ can not be reached.

I can reach the ambassador-admin service via kubectl proxy in the browser at http://localhost:8001/api/v1/namespaces/ambassador/services/ambassador-admin:8877/proxy/ambassador/v0/diag.

The route config seems fine so far:

And I added to my /etc/hosts the minikube IP:
192.168.49.2 myambassador.com