Hi everyone. We're working on deploying Datahub to...
# all-things-deployment
b
Hi everyone. We're working on deploying Datahub to AWS and we're running into something odd. The directions tell us to create two load balancers, but when we run the
helm install datahub from datahub/datahub
command, two "classic" load balancers are created for us. Is this expected? https://datahubproject.io/docs/deploy/aws/#setup-datahub-using-helm . One loadblancer is created for the frontend and one for the api. There is no ingress set up on the EKS cluster.
b
yes, it is expected as service type is set as Load balancer for frontend and gms . • https://github.com/acryldata/datahub-helm/tree/master/charts/datahub/subcharts/datahub-gms#:~:text=service.type,%22LoadBalancer%22https://github.com/acryldata/datahub-helm/tree/master/charts/datahub/subcharts/datahub-frontend#:~:text=service.type,%22LoadBalancer%22 if you wish to implement "ingress" after installing datahub using helm , you need to follow additional steps - https://datahubproject.io/docs/deploy/aws#:~:text=Expose%20endpoints%20using%20a,through%20the%20host%2Dname It will provision ALB type loadbalancer which will act as ingress controller
b
Thank you so much for the response @bumpy-needle-3184