mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-05-04 12:13:19 +00:00
Marty Hernandez Avedon
28acde1f41
* canonicized horizontal-pod-autoscaler * canonicized load-balancer-and-ingress-controller * canonicized workloads-and-pods * canonicized kubernetes-resource-setup
40 lines
2.5 KiB
Markdown
40 lines
2.5 KiB
Markdown
---
|
|
title: ConfigMaps
|
|
---
|
|
|
|
<head>
|
|
<link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-resources-setup/configmaps"/>
|
|
</head>
|
|
|
|
While most types of Kubernetes secrets store sensitive information, [ConfigMaps](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/) 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**.
|
|
1. Go to the cluster that has the workload that should reference a ConfigMap and click **Explore**.
|
|
1. In the left navigation bar, click **More Resources > Core > ConfigMaps**.
|
|
1. Click **Create**.
|
|
1. Enter a **Name** for the Config Map.
|
|
|
|
:::note
|
|
|
|
Kubernetes classifies ConfigMaps as [secrets](https://kubernetes.io/docs/concepts/configuration/secret/), 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.
|
|
|
|
:::
|
|
|
|
1. Select the **Namespace** you want to add Config Map to.
|
|
|
|
1. 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](secrets.md), not a ConfigMap.
|
|
1. 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](workloads-and-pods/deploy-workloads.md).
|