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 20: Installing Consul

  1. True Consul's service mesh works across heterogeneous environments and data centers across different regions.
  2. True In a Consul cluster, the Consul servers can be in Kubernetes or in VMs.
  3. False The Consul members can join an existing Consul cluster from a VM or Kubernetes.
  1. False Consul servers remain within the same data centers but they can communicate with other data center. Consul servers use the WAN protocol.
  2. True Kubernetes can send write requests to any Consul servers, but only the leader Consul server writes that information to the distributed key-value store.
  3. False Consul uses its own key-value database store to maintain the state of Consul clusters. It doesn't use Kubernetes etcd.