In this section, we will further simplify the microservice landscape by replacing the Spring Cloud Gateway with the built-in ingress resource in Kubernetes, reducing the number of supportive services required to be deployed.
As introduced in Chapter 15, Introduction to Kubernetes, an ingress resource can be used in Kubernetes to act as an edge server in the same way as a Spring Cloud Gateway. The Spring Cloud Gateway comes with a richer routing functionality compared to an ingress resource. But the ingress feature is part of the Kubernetes platform and can also be extended using the Cert Manager to automatically provide certificates, as we will see later on in this chapter.
We have also used the Spring Cloud Gateway to protect our microservices from unauthenticated requests; that is, the microservices require a valid...
