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

Creating, deploying, updating, and rolling back a Helm chart

As you can see from the previous example, deploying pre-packaged applications with Helm is pretty simple. Deploying your own application is also easy. We start with the following command, which will create a directory in your current directory called myhelmchart and populate it with the relevant files and templates:

$ helm create myhelmchart

By default, the values.yaml file created by this command contains references to a single NGINX pod and creates a ClusterIP service, which is only accessible from within the cluster. The key values from the default file are shown next:

replicaCount: 1
image:
  repository: nginx
service:
  type: ClusterIP

We can easily deploy this new Helm chart using the following command:

$ helm install example ./myhelmchart --set service.type=NodePort

This will override the service.type value seen in the values.yaml file with a NodePort service, so it is now exposed...