Book Image

Mastering Elastic Kubernetes Service on AWS

By : Malcolm Orr, Yang-Xin Cao (Eason)
5 (1)
Book Image

Mastering Elastic Kubernetes Service on AWS

5 (1)
By: Malcolm Orr, Yang-Xin Cao (Eason)

Overview of this book

Kubernetes has emerged as the de facto standard for container orchestration, with recent developments making it easy to deploy and handle a Kubernetes cluster. However, a few challenges such as networking, load balancing, monitoring, and security remain. To address these issues, Amazon EKS offers a managed Kubernetes service to improve the performance, scalability, reliability, and availability of AWS infrastructure and integrate with AWS networking and security services with ease. You’ll begin by exploring the fundamentals of Docker, Kubernetes, Amazon EKS, and its architecture along with different ways to set up EKS. Next, you’ll find out how to manage Amazon EKS, encompassing security, cluster authentication, networking, and cluster version upgrades. As you advance, you’ll discover best practices and learn to deploy applications on Amazon EKS through different use cases, including pushing images to ECR and setting up storage and load balancing. With the help of several actionable practices and scenarios, you’ll gain the know-how to resolve scaling and monitoring issues. Finally, you will overcome the challenges in EKS by developing the right skill set to troubleshoot common issues with the right logic. By the end of this Kubernetes book, you’ll be able to effectively manage your own Kubernetes clusters and other components on AWS.
Table of Contents (28 chapters)
1
Part 1: Getting Started with Amazon EKS
7
Part 2: Deep Dive into EKS
13
Part 3: Deploying an Application on EKS
20
Part 4: Advanced EKS Service Mesh and Scaling
24
Part 5: Overcoming Common EKS Challenges

Choosing and using different CNIs in EKS

We have seen how AWS CNI integrates with the VPC to offer IP address management (IPAM) services and the creation and management of the Pod network interface. The following are some of the reasons why you might want to replace the default AWS VPC CNI:

  • If you want to have multiple Pod interfaces
  • If you want to use an overlay network for encryption
  • If you want to use network acceleration, such as DPDK or eBPF

As the EKS control plane is managed by AWS, there are a limited number of CNIs supported today; please refer to https://docs.aws.amazon.com/eks/latest/userguide/alternate-cni-plugins.html for the most up-to-date list.

The most important decision you need to make is whether you can extend the existing VPC CNI as we did with Calico but continue to use the VPC CNI to manage IP addresses and Pod interfaces. This is referred to as CNI plugin chaining, where a primary CNI is enhanced with additional capabilities. Therefore...