You're reading from Cloud Native with Kubernetes Deploy, configure, and run modern cloud native applications on Kubernetes

Product type Paperback

Published in Jan 2021

Publisher Packt

ISBN-13 9781838823078

Length 446 pages

Edition 1st Edition

Tools

Jenkins

Concepts

Cloud Native

Author (1):

Alexander Raul

View More author details

Table of Contents (22) Chapters

Preface

1. Section 1: Setting Up Kubernetes

2. Chapter 1: Communicating with Kubernetes FREE CHAPTER

3. Chapter 2: Setting Up Your Kubernetes Cluster

4. Chapter 3: Running Application Containers on Kubernetes

5. Section 2: Configuring and Deploying Applications on Kubernetes

6. Chapter 4: Scaling and Deploying Your Application

7. Chapter 5: Services and Ingress – Communicating with the Outside World

8. Chapter 6: Kubernetes Application Configuration

9. Chapter 7: Storage on Kubernetes

10. Chapter 8: Pod Placement Controls

11. Section 3: Running Kubernetes in Production

12. Chapter 9: Observability on Kubernetes

13. Chapter 10: Troubleshooting Kubernetes

14. Chapter 11: Template Code Generation and CI/CD on Kubernetes

15. Chapter 12: Kubernetes Security and Compliance

16. Section 4: Extending Kubernetes

17. Chapter 13: Extending Kubernetes with CRDs

18. Chapter 14: Service Meshes and Serverless

19. Chapter 15: Stateful Workloads on Kubernetes

20. Assessments

21. Other Books You May Enjoy

Leave a review - let other readers know what you think

Adding a service mesh to Kubernetes

A service mesh pattern is a logical extension of the sidecar proxy. By attaching sidecar proxies to every Pod, a service mesh can control functionality for service-to-service requests, such as advanced routing rules, retries, and timeouts. In addition, by having every request pass through a proxy, service meshes can implement mutual TLS encryption between services for added security and can give administrators incredible observability into requests in their cluster.

There are several service mesh projects that support Kubernetes. The most popular are as follows:

Istio
Linkerd
Kuma
Consul

Each of these service meshes has different takes on the service mesh pattern. Istio is likely the single most popular and comprehensive solution, but is also quite complex. Linkerd is also a mature project, but is easier to configure (though it uses its own proxy instead of Envoy). Consul is an option that supports Envoy in addition...