When I do a kubectl get all -n pinot-quickstart, I...
# getting-startedk
Kaushik Ranganath
06/07/2021, 4:01 AMWhen 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!
Kaushik Ranganath
06/11/2021, 2:54 PMHello all, just trying to get some attention on my question. I wanted to know if there are any implementations in production at all in AWS with Pinot running on EKS clusters! I just want to be able to access the broker and the controller to ingest some sample data. Any resources/inputs are much appreciated!