Book Image

Kubernetes on AWS

By : Ed Robinson
Book Image

Kubernetes on AWS

By: Ed Robinson

Overview of this book

Docker containers promise to radicalize the way developers and operations build, deploy, and manage applications running on the cloud. Kubernetes provides the orchestration tools you need to realize that promise in production. Kubernetes on AWS guides you in deploying a production-ready Kubernetes cluster on the AWS platform. You will then discover how to utilize the power of Kubernetes, which is one of the fastest growing platforms for production-based container orchestration, to manage and update your applications. Kubernetes is becoming the go-to choice for production-grade deployments of cloud-native applications. This book covers Kubernetes from first principles. You will start by learning about Kubernetes' powerful abstractions - Pods and Services - that make managing container deployments easy. This will be followed by a guided tour through setting up a production-ready Kubernetes cluster on AWS, while learning the techniques you need to successfully deploy and manage your own applications. By the end of the book, you will have gained plenty of hands-on experience with Kubernetes on Amazon Web Services. You will also have picked up some tips on deploying and managing applications, keeping your cluster and applications secure, and ensuring that your whole system is reliable and resilient to failure.
Table of Contents (12 chapters)

Managing change

Managing your Kubernetes clusters with a tool like Terraform offers a lot of advantages over the manual approach that we explored in Chapter 3, Reach for the Cloud. Being able to quickly and easily repeat the process of provisioning a cluster is very useful when you want to test changes to your configuration, or even when you come to upgrade the version of Kubernetes that your cluster is running.

The other key advantage of defining your infrastructure as code, is that you can use a version control tool to keep track of the changes that you make to your infrastructure over time. One of the key advantages to this is that every time you make a change, you can leave a commit message. Decisions that you make now might seem obvious, but having a record of why you chose to do something a certain way will certainly help you and others who have to work with your configuration...