You're reading from Microservices with Spring Boot 3 and Spring Cloud, Third Edition Build resilient and scalable microservices using Spring Cloud, Istio, and Kubernetes

Product type Paperback

Published in Aug 2023

Publisher Packt

ISBN-13 9781805128694

Length 706 pages

Edition 3rd Edition

Languages

Java

Tools

Istio

Concepts

Microservices

Author (1):

Magnus Larsson AB

View More author details

Table of Contents (26) Chapters

Preface

1. Introduction to Microservices

2. Introduction to Spring Boot FREE CHAPTER

3. Creating a Set of Cooperating Microservices

4. Deploying Our Microservices Using Docker

5. Adding an API Description Using OpenAPI

6. Adding Persistence

7. Developing Reactive Microservices

8. Introduction to Spring Cloud

9. Adding Service Discovery Using Netflix Eureka

10. Using Spring Cloud Gateway to Hide Microservices behind an Edge Server

11. Securing Access to APIs

12. Centralized Configuration

13. Improving Resilience Using Resilience4j

14. Understanding Distributed Tracing

15. Introduction to Kubernetes

16. Deploying Our Microservices to Kubernetes

17. Implementing Kubernetes Features to Simplify the System Landscape

18. Using a Service Mesh to Improve Observability and Management

19. Centralized Logging with the EFK Stack

20. Monitoring Microservices

21. Installation Instructions for macOS

22. Installation Instructions for Microsoft Windows with WSL 2 and Ubuntu

23. Native-Complied Java Microservices

24. Other Books You May Enjoy

25. Index

Testing with Kubernetes ConfigMaps, Secrets, Ingress, and cert-manager

With the preceding changes described, we are ready to test the system landscape with the Spring Cloud Config Server and the Spring Cloud Gateway replaced by Kubernetes ConfigMaps, Secrets, an Ingress object, and cert-manager. As before, when we used the Spring Cloud Gateway as the edge server, the external API will be protected by HTTPS. With this deployment, it will be the Ingress controller that uses the certificate provisioned by cert-manager to protect the external API with HTTPS. This is illustrated in the following diagram:

Diagram Description automatically generated

Figure 17.3: Protecting external access using HTTPS

The Ingress controller is exposed on the default HTTPS port, 443, on the Minikube instance. On the host, where we run the Minikube instance as a Docker container, we communicate with the Minikube instance via localhost. When the Minikube instance was created, port forwarding was configured from port 8443 on localhost to the...