Skip to main content
Version: v2.10

ConfigMaps

While most types of Kubernetes secrets store sensitive information, ConfigMaps store general configuration information, such as a group of config files. Because ConfigMaps don't store sensitive information, they can be updated automatically, and therefore don't require their containers to be restarted following update (unlike most secret types, which require manual updates and a container restart to take effect).

ConfigMaps accept key value pairs in common string formats, like config files or JSON blobs. After you upload a config map, any workload can reference it as either an environment variable or a volume mount.

  1. In the upper left corner, click ☰ > Cluster Management.

  2. Go to the cluster that has the workload that should reference a ConfigMap and click Explore.

  3. In the left navigation bar, click More Resources > Core > ConfigMaps.

  4. Click Create.

  5. Enter a Name for the Config Map.

    note

    Kubernetes classifies ConfigMaps as secrets, and no two secrets in a project or namespace can have duplicate names. Therefore, to prevent conflicts, your ConfigMaps must have a unique name among the other certificates, registries, and secrets within your workspace.

  6. Select the Namespace you want to add Config Map to.

  7. On the Data tab, add a key-value pair to your ConfigMap. Add as many values as you need. You can add multiple key value pairs to the ConfigMap by copying and pasting. Alternatively, use Read from File to add the data. Note: If you need to store sensitive data, use a secret, not a ConfigMap.

  8. Click Create.

Result: Your ConfigMap is added to the namespace. You can view it in the Rancher UI from the Resources > Config Maps view.

What's Next?​

Now that you have a ConfigMap added to a namespace, you can add it to a workload that you deploy from the namespace of origin. You can use the ConfigMap to specify information for you application to consume, such as:

  • Application environment variables.
  • Specifying parameters for a Volume mounted to the workload.

For more information on adding ConfigMaps to a workload, see Deploying Workloads.