Multi-AZ deployment of Amazon EKS

Introduction

Amazon Elastic Kubernetes Service (EKS) is a managed Kubernetes service provided by Amazon Web Services (AWS). It allows you to deploy, manage, and scale containerized applications using Kubernetes on AWS infrastructure. Multi-AZ (Availability Zone) deployment in Amazon EKS ensures high availability and fault tolerance for your Kubernetes clusters by distributing resources across multiple Availability Zones within an AWS region.

Benefits of Multi-AZ Deployment in Amazon EKS

• High Availability: Distributing your cluster across multiple AZs ensures that your applications remain available in case of an AZ failure.
• Fault Tolerance: If one AZ experiences issues, the workload can be shifted to another AZ, maintaining continuity.
• Improved Performance: Distributing nodes across AZs can enhance the performance of your applications by leveraging resources from multiple locations.
• Automatic Failover: Amazon EKS handles the deployment of nodes across AZs and ensures that your cluster is resilient to failures.

Steps to Deploy Multi-AZ Amazon EKS Cluster

Step 1: Spin up two Amazon EKS clusters in two different regions. Cluster 1 is in Mumbai, and Cluster 2 is in Singapore. The naming convention can be changed according to use case.

Step 2: Create an OIDC provider for both the cluster after the cluster’s creation.

Step 3: Create a policy and service account for the load balancer controller.

Step 4: Create a load balancer controller with helm Amazon EKS charts and deploy it in both clusters. It will be visible in the kube-system namespace.

Step 5: Deploy a sample application in both the clusters and ingress to create load balancers for public access.

Step 6: Create a global accelerator, add a listener with endpoint groups for the two regions used, and add an endpoint for the ingress load balancer. Set traffic dial for the Mumbai region to 100% and the Singapore region to 0%.

Step 7: After creating the global accelerator is completed, check the listener rule for the healthy and unhealthy status of the load balancer. Check the accessibility in the browser.

Step 8: Stop the running sample application in the Singapore region and check the health status again. There will be 30 seconds of downtime before it routes to the healthy listener.

Healthy listener

Unhealthy listener

Conclusion

In conclusion, deploying a multi-AZ Amazon EKS cluster provides a robust foundation for running containerized applications with high availability and fault tolerance on the AWS cloud. Leveraging the managed Kubernetes service, Amazon EKS, and the eksctl command-line utility streamlines the process of creating and managing clusters, allowing you to focus on your applications rather than the underlying infrastructure. As you embark on your journey with multi-AZ Amazon EKS clusters, stay informed about the latest AWS updates and best practices. Regularly consult the official documentation for any changes or optimizations that may enhance the security, performance, and efficiency of your Kubernetes workloads on Amazon EKS.

Drop a query if you have any questions regarding Amazon EKS cluster and we will get back to you quickly.

About CloudThat