- Newest
- Most votes
- Most comments
Hi jeffp2016,
You can manually create, maintain and manage a Load Balancer without Kubernetes control. Thereafter, you can associate the Load Balancer with your ECS/EKS using the TargetGroupBinding attribute.
TargetGroupBinding feature enables you to expose your Kubernetes applications to the external clients through an already existing target group on the AWS Elastic Load Balancer, which was provisioned through AWS console / AWS CLI / CloudFormation etc. What this gives you is the flexibility and independence so that you do not need to use a native method such as Kubernetes service type of Load Balancer or Kubernetes Ingress to expose your application(s) to external clients.
This approach basically introduces decoupling between Kubernetes services/ingress and the AWS Network or Application load balancer used in the environment.
For your convenience, the link below provides a step by step guide to the same implementation/solution: https://catalog.workshops.aws/eks-immersionday/en-US/services-and-ingress/targetgroupbinding
Relevant content
- asked 10 months ago
- AWS OFFICIALUpdated 9 months ago
- How can I troubleshoot issues when I use the AWS Load Balancer Controller to create a load balancer?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 5 months ago
But there isnt a way to share an ALB and allow the AWS Load Balancer Controller to use that and create target groups for that? We have full apps (like, Vault, or PaperLess, or Rancher, or EJBCA, etc) not microservices we are looking to run/setup. Each 'thing' that needs something from the LB Controller is a full system and has a distinguished URL.
But, the other info to not only share an LB and a single target group is interesting, thank you.