Skip to content

Add new project scoped secret documentation #1834

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

JonCrowther
Copy link
Contributor

Fixes #1626

Reminders

  • See the README for more details on how to work with the Rancher docs.

  • Verify if changes pertain to other versions of Rancher. If they do, finalize the edits on one version of the page, then apply the edits to the other versions.

  • If the pull request is dependent on an upcoming release, remember to add a "MERGE ON RELEASE" label and set the proper milestone.

Description

Project scoped secrets used to be part of the legacy features in Rancher, but in v2.12 we are adding it to the regular Rancher UI. I've added documentation to help users use the new UI and to create a project scoped secret manually.

Comments

The feature is still located in the legacy UI for versions prior to v2.12, so I've left the documentation as the same for those versions.

Copy link
Contributor

@pmkovar pmkovar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR.

@pmkovar pmkovar added MERGE ON RELEASE Don't merge until the moment the next release publishes DO NOT MERGE labels Jun 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DO NOT MERGE MERGE ON RELEASE Don't merge until the moment the next release publishes port/community-product
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update Project Scoped Secret information
3 participants