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)

Storing data inside your cluster with StatefulSets

It's best to store data within your Kubernetes cluster. This provides a uniform one-stop shop to manage your workloads and all the resources they depend on (excluding third-party external services). Additionally, you get to integrate your storage with your streamlined monitoring, which is very important. We will discuss monitoring in depth in a future chapter. However, running out of disk space is the bane of many system administrators. But there is a problem if you store data on a node and your data store pods get rescheduled to a different node, and the data it expects to be available is not there. The Kubernetes designers realized that the ephemeral pod philosophy doesn't work for storage. You could try to manage it yourself using pod-node affinity and other mechanisms that Kubernetes provides, but it's much...