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)

Resource requests and limits

Kubernetes allows us to achieve high utilization of our cluster by scheduling multiple different workloads to a single pool of machines. Whenever we ask Kubernetes to schedule a pod, it needs to consider which node to place it on. The scheduler can make much better decisions about where to place a pod if we can give it some information about the resources that the pod will need; it then can calculate the current workload on each node and choose the node that fits the expected resource usage of our pod. We can optionally give Kubernetes this information with resource requests. Requests are considered at the time when a pod is scheduled to a node. Requests do not provide any limit to the amount of resources a pod may consume once it is running on a particular node, they just represent an accounting of the requests that we, the cluster operator, made...