Skip to content

Latest commit

 

History

History
44 lines (30 loc) · 1.82 KB

README.md

File metadata and controls

44 lines (30 loc) · 1.82 KB
Raw

ConfigMaps

ConfigMaps are K8S' means to externalize configuration from your application code. They are essentially key/value pairs that can be defined in a single file, a directory of files or just simple literal values from the command line. Configmaps are key value/pairs. If the datasource is a file, the key is the filename and the value is the content of the file.

To create a config map from a file run:

kubectl create configmap app-config --from-file=application.properties

Get the content of a configmap like so:

kubectl get configmap app-config -o=yaml

Of course, as ConfigMaps are just resources, you can define a ConfigMap manifest with key/value pairs.

apiVersion: v1
kind: ConfigMap
metadata:
  name: app-properties
  namespace: default
data:
  log_level: DEBUG

Note: ConfigMaps are not for credentials and keys. They are meant for environment and application specific configuration data. Use secrets for credentials and keys.

Accessing ConfigMap Data from Pods

There are two primary approaches to access your configuration data from the containers within your Pods. As environment variables and as a file in a volume. You specify the approach within your pod template. See the Use ConfigMap Data in Pods at K8S.io.

Also see:

References