public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 20:48:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Clarify that project-scoped secrets can't be set at the namespace level

Browse Source
This commit is contained in:
Caleb Bron
2023-02-27 16:44:04 -07:00
parent df7d053f16
commit 64f9e1b790
2 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/how-to-guides/new-user-guides/kubernetes-resources-setup/secrets.md
+2
View File
@@ -63,6 +63,8 @@ Before v2.6, secrets were required to be in a project scope. Projects are no lon
**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**.
Since project-scoped secrets are set at the project level, any changes made at the namespace level will be overwritten.
:::note
Project-scoped secrets on the local cluster are only visible when a single project is selected.