Our software applications are hosted on Kubernetes, and we utilize various microservices such as Spring Boot, Fastify, and Go. Due to this diverse setup, utilizing the Spring Config Server directly may not be suitable for our needs. As a solution, we have instructed all application teams to adhere to a specific convention. They are now responsible for maintaining all configuration YAML files within a designated "config" folder in their respective repositories.
To streamline the process, we have integrated a node module into our CI/CD pipeline. This module merges all the configuration files located in the config folder, taking into account environment-specific flavors. Subsequently, we mount the resulting config map onto our pods. This enables the application teams to dynamically access and utilize the properties contained within the configuration files.