Book Image

Hands-On Microservices with Kubernetes

By : Gigi Sayfan
Book Image

Hands-On Microservices with Kubernetes

By: Gigi Sayfan

Overview of this book

Kubernetes is among the most popular open source platforms for automating the deployment, scaling, and operations of application containers across clusters of hosts, providing a container-centric infrastructure. Hands-On Microservices with Kubernetes starts by providing you with in-depth insights into the synergy between Kubernetes and microservices. You will learn how to use Delinkcious, which will serve as a live lab throughout the book to help you understand microservices and Kubernetes concepts in the context of a real-world application. Next, you will get up to speed with setting up a CI/CD pipeline and configuring microservices using Kubernetes ConfigMaps. As you cover later chapters, you will gain hands-on experience in securing microservices and implementing REST, gRPC APIs, and a Delinkcious data store. In addition to this, you’ll explore the Nuclio project, run a serverless task on Kubernetes, and manage and implement data-intensive tests. Toward the concluding chapters, you’ll deploy microservices on Kubernetes and learn to maintain a well-monitored system. Finally, you’ll discover the importance of service meshes and how to incorporate Istio into the Delinkcious cluster. By the end of this book, you’ll have gained the skills you need to implement microservices on Kubernetes with the help of effective tools and best practices.
Table of Contents (16 chapters)

Autoscaling a Kubernetes cluster

Autoscaling is all about adapting your system to demand. This can mean adding more replicas to a deployment, expanding the capacity of existing nodes, or adding new nodes. While scaling your cluster up or down is not a failure, it follows the same pattern as self-healing. You can consider a cluster that is misaligned with demand as unhealthy. If the cluster is underprovisioned, then requests are not handled or wait too long, which can lead to timeouts or just poor performance. If the cluster is overprovisioned, then you're paying for resources you don't need. In both cases, you can consider the cluster as unhealthy, even if the pods and services themselves are up and running.

Just like with self-healing, you first need to detect that you need to scale your cluster, and then you can take the correct action. There are several ways to scale...