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)

Technical requirements

In this chapter, we will work with Istio. I chose to use Google Kubernetes Engine (GKE) in this chapter because Istio can be enabled on GKE as an add-on and doesn't require you to install it. This has the following two benefits:

  • It saves time on installation
  • It demonstrates that Delinkcious can run in the cloud and not just locally

To install Istio, you simply have to enable it in the GKE console and select an mTLS mode, which is the mutual authentication between services. I chose permissive, which means that the internal communication inside the cluster is not encrypted by default, and the services will accept both encrypted and non-encrypted connections. You can override it per service. For production clusters, I recommend using the strict mTLS mode, where all connections must be encrypted:

Istio gets installed in its own istio-system namespace...