Book Image

Mastering Kubernetes - Third Edition

By : Gigi Sayfan
Book Image

Mastering Kubernetes - Third Edition

By: Gigi Sayfan

Overview of this book

The third edition of Mastering Kubernetes is updated with the latest tools and code enabling you to learn Kubernetes 1.18’s latest features. This book primarily concentrates on diving deeply into complex concepts and Kubernetes best practices to help you master the skills of designing and deploying large clusters on various cloud platforms. The book trains you to run complex stateful microservices on Kubernetes including advanced features such as horizontal pod autoscaling, rolling updates, resource quotas, and persistent storage backend. With the two new chapters, you will gain expertise in serverless computing and utilizing service meshes. As you proceed through the chapters, you will explore different options for network configuration and learn to set up, operate, and troubleshoot Kubernetes networking plugins through real-world use cases. Furthermore, you will understand the mechanisms of custom resource development and its utilization in automation and maintenance workflows. By the end of this Kubernetes book, you will graduate from an intermediate to advanced Kubernetes professional.
Table of Contents (19 chapters)
17
Other Books You May Enjoy
18
Index

What is a service mesh?

A service mesh is an architectural pattern for large-scale cloud native applications that are composed of many microservices. When your application is structured as a collection of microservices, there is a lot going on in the boundary between the microservices internally, inside your Kubernetes cluster.

This is different from traditional monolithic applications, where most of the processing is within the same process.

Here are some of the concerns that are relevant for each microservice or interaction between microservices:

  • Advanced load balancing
  • Service discovery
  • Support canary deployments
  • Caching
  • Tracing a request across multiple microservices
  • Authentication between services
  • Throttling the number requests a service handles at a given time
  • Automatically retrying failed requests
  • Failing over to an alternative component when a component fails consistently
  • Collecting metrics
...