From f738dc7a07b300a87a5795663dbae5cc5cc0b670 Mon Sep 17 00:00:00 2001 From: Adrian Goins Date: Thu, 20 Jun 2019 08:44:53 -0400 Subject: [PATCH] update formatting and remove duplicate text --- .../v2.x/en/k8s-in-rancher/secrets/_index.md | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/content/rancher/v2.x/en/k8s-in-rancher/secrets/_index.md b/content/rancher/v2.x/en/k8s-in-rancher/secrets/_index.md index 284ee126dfa..5b958d9dcb5 100644 --- a/content/rancher/v2.x/en/k8s-in-rancher/secrets/_index.md +++ b/content/rancher/v2.x/en/k8s-in-rancher/secrets/_index.md @@ -6,29 +6,28 @@ aliases: --- [Secrets](https://kubernetes.io/docs/concepts/configuration/secret/#overview-of-secrets) store sensitive data like passwords, tokens, or keys. They may contain one or more key value pairs. + When configuring a workload, you'll be able to choose which secrets to include. Like config maps, secrets can be referenced by workloads as either an environment variable or a volume mount. ->**Note:** Any update to secrets won't reflect automatically inside pods, until the pods are restarted. - -[Secrets](https://kubernetes.io/docs/concepts/configuration/secret/#overview-of-secrets) store sensitive data like passwords, tokens, or keys. They may contain one or more key value pairs. +>**Note:** Any update to an active secrets won't automatically update the pods that are using it. Restart those pods to have them use the new secret. When creating a secret, you can make it available for any deployment within a project, or you can limit it to a single namespace. 1. From the **Global** view, select the project containing the namespace(s) where you want to add a secret. -1. From the main menu, select **Resources > Secrets**. Click **Add Secret**. +2. From the main menu, select **Resources > Secrets**. Click **Add Secret**. -1. Enter a **Name** for the secret. +3. Enter a **Name** for the secret. >**Note:** Kubernetes classifies secrets, certificates, ConfigMaps, and registries all 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 secret must have a unique name among all secrets within your workspace. -1. Select a **Scope** for the secret. You can either make the registry available for the entire project or a single [namespace]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/#namespaces). +4. Select a **Scope** for the secret. You can either make the registry available for the entire project or a single [namespace]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/#namespaces). -1. From **Secret Values**, click **Add Secret Value** to add a key value pair. Add as many values as you need. +5. From **Secret Values**, click **Add Secret Value** to add a key value pair. Add as many values as you need. - >**Tip:** You can add multiple key value pairs to the secret by copying and pasting. - > - > ![Bulk Key Value Pair Copy/Paste]({{< baseurl >}}/img/rancher/bulk-key-values.gif) + >**Tip:** You can add multiple key value pairs to the secret by copying and pasting. + > + > ![Bulk Key Value Pair Copy/Paste]({{< baseurl >}}/img/rancher/bulk-key-values.gif) 1. Click **Save**.