From 68c2bf1d3a6dfbdfda7829da9e02a9d4c8d9bec6 Mon Sep 17 00:00:00 2001 From: Jennifer Travinski Date: Tue, 16 Nov 2021 15:41:54 -0500 Subject: [PATCH] Updated directions for secrets --- content/rancher/v2.6/en/k8s-in-rancher/secrets/_index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/rancher/v2.6/en/k8s-in-rancher/secrets/_index.md b/content/rancher/v2.6/en/k8s-in-rancher/secrets/_index.md index ff7b9a391df..69a14af98e3 100644 --- a/content/rancher/v2.6/en/k8s-in-rancher/secrets/_index.md +++ b/content/rancher/v2.6/en/k8s-in-rancher/secrets/_index.md @@ -52,6 +52,8 @@ Prior to v2.6, secrets were required to be in a project scope. Projects are no l **Result:** Your secret is added to the individual project you chose. You can view the secret in the Rancher UI by clicking either **Storage > Secrets** or **More Resources > Core > Secrets**. +>**Note:** Project-scoped secrets on the local cluster are only visible when a single project is selected. + # What's Next? Now that you have a secret added to a namespace, you can add it to a workload that you deploy.