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 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.
From the Global view, select the project containing the namespace(s) where you want to add a secret.
From the main menu, select Resources > Secrets. Click Add Secret.
Enter a Name for the secret.
Note: Kubernetes classifies secrets, certificates, ConfigMaps, and registries all as secrets, 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.
Select a Scope for the secret. You can either make the registry available for the entire project or a single namespace.
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.
- Click Save.
Result: Your secret is added to the project or namespace, depending on the scope you chose. You can view the secret in the Rancher UI from the Resources > Secrets view.
Now that you have a secret added to the project or namespace, you can add it to a workload that you deploy.
For more information on adding secret to a workload, see Deploying Workloads.