[v2.11] Add documentation for aggregated clusterroles #1649
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JonCrowther
added
the
MERGE ON RELEASE
JonCrowther
requested review from
btat,
LucasSaintarbor and
sunilarjun
as code owners
aruiz14
approved these changes
Feb 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Original rancher/rancher issue: rancher/rancher#46077
Description
There is a new feature
ClusterRole Aggregation. Currently it's only in Rancher v2.11 in order to allow our QA team to begin testing. It's hidden behind a feature flag for now, so I added information about the feature flag in the documentation. I also added a new page in theenable-experimental-featuresdirectory giving more details about the feature.Comments
The page related to the feature is pretty sparse, but that's largely because it's still in progress. While the overall architecture is set, the details aren't finalized and may change after testing. My primary goal is to discourage users from using this new feature without understanding that it is not well supported. When it's more ready (likely in v2.12) I will create a more comprehensive feature page.