Replacing the Spring Cloud Config Server

As we have seen in the previous chapter, Chapter 16, Deploying Our Microservices to Kubernetes, in the Deploying to Kubernetes section, config maps and secrets can be used to hold configuration information for our microservices. The Spring Cloud Config Server adds values such as keeping all configuration in one place, optional version control using Git, and the ability to encrypt sensitive information on the disk. But it also consumes a non-negligible amount of memory (as with any Java and Spring-based application) and adds significant overhead during startup. For example, when running automated integration tests such as the test script we are using in this book, test-em-all.bash, all microservices are started up at the same time, including the configuration server. Since the other microservices must get their configuration from...