Member-only story
In this blog, we will explore how we can use the the configuration data like database details using Config Maps and Secrets.
Application ( Container Image) -> Deploy it on the Dev -> INT -> Prod
There is no change from the application, application remains the same in all the environments. The only thing which will change is the database details. So we need to make our application code in such a way that we can provide the environment specific data separately.
Kubernetes provides to associate environment-specific data with our application containers without changing our container image.
Config Map
- Used to define application-related data
- It decouples the application data from the application so that the same application can be ported across different environments.
- provides a way to inject customized data into running services from the same container image.
- used for non-sensitive configuration
kubectl create configmap --help
