When I do a kubectl get all -n pinot-quickstart, I...
# troubleshooting
k
When I do a kubectl get all -n pinot-quickstart, I see this has brought up classic load balancers to expose both the broker and the controller on tcp ports, and when I make a curl/browser request to the DNSs, I expect these to show up the UI for the broker and the Swagger UI for the controller, but the request times out eventually without bringing up the UI. I am a beginner in AWS Networking as well, but the security groups created by these setup instructions which I have followed exactly allows TCP requests from 0.0.0.0/0. Any inputs on bringing the UI up for the broker and server are much appreciated!
d
Did you get any reply to this? I am facing the same issue. I have setup Pinot on K8S on Azure. All services are running. Broker and Controller have their external IP addresses as well but I am not able to access them from the browser. Any tips will be super helpful. Thanks!