In this chapter, we have seen how capabilities in Kubernetes can be used to simplify a microservice landscape, meaning that we reduce the number of support services to be developed and deployed together with the microservices. We have seen how Kubernetes config maps and secrets can be used to replace the Spring Cloud Config Server and how a Kubernetes ingress can replace an edge service based on Spring Cloud Gateway.
Using the Cert Manager together with Let's Encrypt allowed us to automatically provision certificates for HTTPS endpoints exposed by the ingress, eliminating the need for manual and cumbersome work. Since our Kubernetes cluster running in a local Minikube instance isn't available from the internet, we used ngrok to establish an HTTP tunnel from the internet to the Minikube instance. The HTTP tunnel was used by Let's Encrypt to verify...
