<p>According to the Kubernetes docs <a href="https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/" rel="noreferrer">K8s Docs</a> as of v1.6 and later we are able to use:</p>
<pre><code>envFrom:
  - configMapRef:
      name: &lt;config-file&gt;
</code></pre>
<p>To define all the configMaps data as container env variables. What is the use case for using this versus setting it as an env variable with the name and key:</p>
<pre><code>env:
        # Define the environment variable
        - name: SPECIAL_LEVEL_KEY
          valueFrom:
            configMapKeyRef:
              # The ConfigMap containing the value you want to assign to SPECIAL_LEVEL_KEY
              name: special-config
              # Specify the key associated with the value
              key: special.how
</code></pre>
<p>Would you use the second example if you had multiple variables in the file but only wanted to pull out a single key=value pair? I am trying to understand different use cases for scenarios I may encounter on the CKAD exam.</p>

<p>I have used both and some of my deployments used tens of environment variables. It depends very much of your specifics and the way you manage your settings.</p>
<p>In general if you have specific configmaps for specific applications where your application uses all or most of the keys in the configmaps, then <code>envFrom</code> is obviously easier the use and maintain. When one of your teammate needs to add a new feature flag for example, simply adding it to the configmap is enough to enable it on all your deployments.</p>
<p>In an other hand, if you organize your configmaps more by theme or if multiple applications need specific keys from the same configmap, then <code>configMapKeyRef</code> is better. You will take only the keys you need in your application and ensure that nothing will be overwritten accidentally. The downside being that your teammate, in order to add the same feature flag, will now have to edit the configmap and the deployments.</p>
<p>Keep it mind that both options are not exclusive and you will probably end up using a mixture of both. For example something like this might make sense:</p>
<pre class="lang-yaml prettyprint-override"><code>envFrom:
    # This might contain environment-wide settings. Like the domain name that your application uses or a production only feature flag.
  - configMapRef:
      name: production-settings
    # Here you could store all the settings of this specific application.
  - configMapRef:
      name: my-app-settings
env:
  # This might be a bucket shared by multiple applications. So you might want to keep it a different configmap and let each aplication pick the keys they need.
  - name: S3_BUCKET
    valueFrom:
      configMapKeyRef:
        name: s3-settings
        key: bucket
</code></pre>
