AWS Load Balancer Controller overview | Reuse the same ALB for multiple Ingress resources

[@zmxn007]

Very simple but good explanation of AWS ALB controller feature. Thank you.

[@visa2learn]

Glad it was helpful!

[@DavidGraves]

Finally a clear and concise overview. Thank you for this video (after having watched at least a dozen or more)

[@visa2learn]

Thanks, glad to hear it was helpful.

[@buzzuti]

Wonderfully concise summary.
This helped me wrap my head around AWS Load Balancer Controllers.

[@visa2learn]

Thanks. Glad it was helpful :)

[@OsascogamingBrSP]

Thank you! It helped me a lot!

[@visa2learn]

Glad to hear

[@hamidullahmuslih6301]

amazing work man!

[@visa2learn]

Thanks a lot!

[@cloudemotive]

Nice , thanks for sharing :)

[@visa2learn]

Glad you liked it. Thanks for watching :)

[@segunsaka-aiyedun8342]

wow thank you so much

[@visa2learn]

Happy to help

[@itshgirish]

Very clear, exactly what i needed .. Thank you!. Just for my understanding, am a noob, internal microservices can continue referring to each other with the metadata.name?

[@visa2learn]

Thanks and glad you liked it. If your question is whether microservices deployed in k8s cluster can refer each other using their service name, then yes they can connect with each other using the Service (provided there is no explicit NetworkPolicy blocking such access). Refer the documentation kubernetes.io/docs/concepts/services-networking/dns-pod-service/ for more information. In short, you can access a service using servicename.namespace.svc.cluster.local

[@itshgirish]

@@visa2learn understood ..
thank you :)

[@rudranil29]

You should show how to deploy ALB controller.

[@visa2learn]

Yes its in my list of upcoming videos. Please stay tuned

[@rritsoftwaresolutions9566]

u shall making a video through practical is it help full