Book Image

Mastering Service Mesh

By : Anjali Khatri, Vikram Khatri
Book Image

Mastering Service Mesh

By: Anjali Khatri, Vikram Khatri

Overview of this book

Although microservices-based applications support DevOps and continuous delivery, they can also add to the complexity of testing and observability. The implementation of a service mesh architecture, however, allows you to secure, manage, and scale your microservices more efficiently. With the help of practical examples, this book demonstrates how to install, configure, and deploy an efficient service mesh for microservices in a Kubernetes environment. You'll get started with a hands-on introduction to the concepts of cloud-native application management and service mesh architecture, before learning how to build your own Kubernetes environment. While exploring later chapters, you'll get to grips with the three major service mesh providers: Istio, Linkerd, and Consul. You'll be able to identify their specific functionalities, from traffic management, security, and certificate authority through to sidecar injections and observability. By the end of this book, you will have developed the skills you need to effectively manage modern microservices-based applications.
Table of Contents (31 chapters)
1
Section 1: Cloud-Native Application Management
4
Section 2: Architecture
8
Section 3: Building a Kubernetes Environment
10
Section 4: Learning about Istio through Examples
18
Section 5: Learning about Linkerd through Examples
24
Section 6: Learning about Consul through Examples

Chapter 9: Installing Istio

  1. True – At the time of writing, Istio can only be used in a Kubernetes environment, though integration with VMs is being planned.
  2. False The Istio sidecar can be enabled for new applications if the namespace is annotated with the istio-injection=enabled label. The sidecar can be enabled through the istioctl command.
  3. True Istio has more than 57 CRDs.
  4. True It is necessary to install CRDs to extend Kubernetes so that it can use Istio's features.
  5. True The existing application needs to be taken down first and then you need to enable sidecar proxy injection, either by annotating the namespace with a label or by using istioctl kube-inject to modify the existing application's manifest.
  6. False It is possible to disable the sidecar for a microservice by setting the pod annotation to sidecar.istio.io...