The following diagram shows our final architecture: To get started, we’ll create an Amazon EKS cluster and a Fargate profile (which allows us to launch pods on Fargate), implement IAM roles for service accounts on our cluster in order to give fine-grained IAM permissions to our ingress controller pods, deploy a simple nginx service, and expose it to the internet using an ALB. You can learn more about the details of Kubernetes ingress with the ALB Ingress controller in our post here. In this blog, we’ll show you how to setup AWS Application Load Balancer (ALB) with your EKS cluster for ingress-based load balancing to Fargate pods using the open source ALB Ingress Controller. Amazon Elastic Load Balancing Application Load Balancer (ALB) is a popular AWS service that load balances incoming traffic at the application layer (layer 7) across multiple targets, such as pods running on a Kubernetes cluster and is a great way to get traffic to such microservices. When your pods start, Fargate automatically allocates compute resources on-demand to run them.įargate is great for running and scaling microservices – especially those with spikey, unpredictable traffic patterns. Fargate eliminates the need for you to create or manage EC2 instances for your Kubernetes applications. In December 2019, we announced the ability to use Amazon Elastic Kubernetes Service to run Kubernetes pods on AWS Fargate.
0 Comments
Leave a Reply. |