<p>Many applications require configuration via some combination of config files, command line arguments, and environment variables. These configuration artifacts should be decoupled from image content in order to keep containerized applications portable. The ConfigMap API resource provides mechanisms to inject containers with configuration data while keeping containers agnostic of Kubernetes. ConfigMap can be used to store fine-grained information like individual properties or coarse-grained information like entire config files or JSON blobs.</p>

<p>I am unable to find where configmaps are saved. I know they are created however I can only read them via the minikube dashboard.</p>

<p><a href="https://kubernetes.io/docs/user-guide/configmap/" rel="nofollow noreferrer">ConfigMaps</a> in Kubernetes can be consumed in many different ways and mounting it as a volume is one of those ways.</p>

<p>You can choose where you would like to mount the ConfigMap on your Pod. Example from K8s documentation:</p>

<p>ConfigMap:</p>

<pre><code>apiVersion: v1
kind: ConfigMap
metadata:
  name: special-config
  namespace: default
data:
  special.how: very
  special.type: charm
</code></pre>

<p>Pod</p>

<pre><code>apiVersion: v1
kind: Pod
metadata:
  name: dapi-test-pod
spec:
  containers:
    - name: test-container
      image: gcr.io/google_containers/busybox
      command: [ "/bin/sh", "-c", "cat /etc/config/special.how" ]
      volumeMounts:
      - name: config-volume
        mountPath: /etc/config
  volumes:
    - name: config-volume
      configMap:
        name: special-config
  restartPolicy: Never
</code></pre>

<p>Note the volumes definition and the corresponding volumeMounts.</p>

<p>Other ways include:</p>

<ul>
<li>Consumption via environment variables</li>
<li>Consumption via command-line arguments</li>
</ul>

<p>Refer to the <a href="https://kubernetes.io/docs/user-guide/configmap/" rel="nofollow noreferrer">documentation</a> for full examples.</p>
