You're reading from The Ultimate Docker Container Book Build, test, ship, and run containers with Docker and Kubernetes

Product type Paperback

Published in Aug 2023

Publisher Packt

ISBN-13 9781804613986

Length 626 pages

Edition 3rd Edition

Tools

Docker

Concepts

DevOps

Author (1):

Dr. Gabriel N. Schenker

View More author details

Table of Contents (26) Chapters

Preface

1. Part 1:Introduction

2. Chapter 1: What Are Containers and Why Should I Use Them? FREE CHAPTER

3. Chapter 2: Setting Up a Working Environment

4. Part 2:Containerization Fundamentals

5. Chapter 3: Mastering Containers

6. Chapter 4: Creating and Managing Container Images

7. Chapter 5: Data Volumes and Configuration

8. Chapter 6: Debugging Code Running in Containers

9. Chapter 7: Testing Applications Running in Containers

10. Chapter 8: Increasing Productivity with Docker Tips and Tricks

11. Part 3:Orchestration Fundamentals

12. Chapter 9: Learning about Distributed Application Architecture

13. Chapter 10: Using Single-Host Networking

14. Chapter 11: Managing Containers with Docker Compose

15. Chapter 12: Shipping Logs and Monitoring Containers

16. Chapter 13: Introducing Container Orchestration

17. Chapter 14: Introducing Docker Swarm

18. Chapter 15: Deploying and Running a Distributed Application on Docker Swarm

19. Part 4:Docker, Kubernetes, and the Cloud

20. Chapter 16: Introducing Kubernetes

21. Chapter 17: Deploying, Updating, and Securing an Application with Kubernetes

22. Chapter 18: Running a Containerized Application in the Cloud

23. Chapter 19: Monitoring and Troubleshooting an Application Running in Production

24. Index

Why subscribe?

25. Other Books You May Enjoy

Context-based routing

Often, we want to configure context-based routing for our Kubernetes cluster. Kubernetes offers us various ways to do this. The preferred and most scalable way currently is to use IngressController. The following diagram tries to illustrate how this ingress controller works:

Figure 16.24 – Context-based routing using a Kubernetes ingress controller

In the preceding diagram, we can see how context-based (or layer 7) routing works when using an IngressController, such as Nginx. Here, we have the Deployment of an application service called web. All the pods of this application service have the following label: app=web. Then, we have a Kubernetes Service called web that provides a stable endpoint to those pods. The Service has a VIP of 52.14.0.13 and exposes a 30044 port. That is, if a request comes to any node of the Kubernetes cluster for the name web and 30044 port, then it is forwarded to this Service. The Service then load...