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

Summary

In this chapter, we explored what Fargate is and how it works. You learned that Fargate is an AWS-managed service, so you really only need to focus on the Fargate profile and make sure that VPC networking and, optionally, load balancers are set up correctly for it all to work.

We also explored the technology and discovered that under the hood, Fargate uses a Firecracker MicroVM to provide complete isolation between your Pod and other Pods even if these are in the same cluster.

We reviewed how the Fargate profile is used to match Pod spec labels and namespaces in the profile and assign them to the Fargate scheduler, which handles the orchestration with the AWS Fargate service to provision your Pod on a Fargate MicroVM and connect it to your VPC.

We then looked at how you can use a Pod or deployment manifest unchanged by just matching the namespace and/or labels defined in the Fargate profile namespace. We also learned that adjusting the Limits or Requests resources...