From f43cd13e6bbe3c793386d96722fe7eb01840c2e3 Mon Sep 17 00:00:00 2001 From: "Jason L. van Brackel" Date: Tue, 3 Jul 2018 13:31:13 -0400 Subject: [PATCH] Changed "Certificate" words to "Config Map" --- .../rancher/v2.x/en/tasks/projects/add-configmaps/_index.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/content/rancher/v2.x/en/tasks/projects/add-configmaps/_index.md b/content/rancher/v2.x/en/tasks/projects/add-configmaps/_index.md index df5301628ad..a3e97507150 100644 --- a/content/rancher/v2.x/en/tasks/projects/add-configmaps/_index.md +++ b/content/rancher/v2.x/en/tasks/projects/add-configmaps/_index.md @@ -10,14 +10,12 @@ ConfigMaps store general configuration information for an application, such as c 1. From the **Global** view, select the project containing the namespace that you want to add a ConfigMap to. -1. From the main menu, select **Resources > Certificates**. Click **Add Certificate**. +1. From the main menu, select **Resources > Config Maps**. Click **Add Config Map**. -1. Enter a **Name** for the certificate. +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, ConfigMaps, registries, and secrets within your workspace. -1. Click on **Add Config Map** option and give it a name. - 1. Select the **Namespace** you want to add Config Map to. You can also add a new namespace on the fly by clicking **Add to a new namespace**. 1. From **Config Map Values**, click **Add Config Map Value** to add a key value pair to your ConfigMap. Add as many values as you need.