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 14: Understanding the Linkerd Service Mesh

  1. True Linkerd has an automatic protocol and TCP connection detection.
  2. False Linkerd does not provide its own ingress controller.
  3. False The Linkerd proxy is written in Rust, while control plane components are written in Go.
  4. True The control and data planes can be in a single namespace if we want them to be. Note that admin privileges are required to create CRDs.
  5. True When a Linkerd proxy is injected into a running pod using the linkerd inject command, the pod is restarted automatically.
  6. False The pod will be recreated if we want to add a debug sidecar.
  7. True – The retry budget helps us avoid a retry storm. We don't need to configure Linkerd to achieve this.
  8. True For automatic sidecar injection, Istio needs a namespace to be labeled with istio-injection=enabled...