Mastering the Move: EKS to AKS by Example - Part 2

Introduction

Welcome back to our series on migrating Amazon Elastic Kubernetes Service (EKS) workloads to Azure Kubernetes Service (AKS). In Part 1 we explored migrating and Event Driven Workload using Karpenter and KEDA from EKS to AKS. Next, we look into a more complex migration scenario with a common Kubernetes workload the n-tier web application.

EKS to AKS - Web Application Scenario

This new article guides you through replicating an application hosted on Amazon EKS with AWS Web Application Firewall (WAF) to Azure. You will learn how to host the application on AKS with Azure WAF and Azure Application Gateway to protect a Yelb web-based application running in a Kubernetes cluster.

In this guide, we explore the deployment process, starting with understanding the conceptual differences between EKS and AKS for the web application workload infrastructure. We then move on to architecting the workload for Azure, updating the application code for compatibility with Azure APIs, and preparing for deployment using the Azure CLI. Finally, we deploy the replicated workload in AKS and test it to ensure it functions as expected.

The guide also include detailed AWS service by Azure service discussion and details alternative solutions for managing ingress including Application Gateway Ingress Controller (AGIC), Azure Application Gateway for Containers, Azure Front Door (AFD), and a NGINX ingress controller with end-to-end TLS configured using Azure Key Vault.

Looking Forward

Our next article will explore migrating an EKS AI/ML workload to AKS. We’ll look at migration challenges common with AI/ML workloads like cost optimization, efficient scaling, and GPU usage.

As always, we are interested to hear about the migration challenges and scenarios you encounter, so we can continue to enhance the features and documentation for AKS to ease the transition from on-premises or other clouds to Azure. Please share your ideas using one of the contact methods below.