docs: Add documentation for the roleGroups CRD field.#1227
Merged
Conversation
lfrancke
force-pushed
the
push-sqnmrxlpoyus
branch
from
June 19, 2026 22:07
a471a55 to
0b452ba
Compare
lfrancke
moved this from Development: In Progress
to Development: Waiting for Review
in Stackable Engineering
sbernauer
approved these changes
Jun 22, 2026
sbernauer
moved this from Development: Waiting for Review
to Development: In Review
in Stackable Engineering
lfrancke
moved this from Development: In Review
to Development: Done
in Stackable Engineering
This was referenced Jun 22, 2026
Merged
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
The generated CRDs don't show documentation for roleGroups. This is mostly taken from the current docs roles concept page.
I ran the
typostool and it stumbled over something that was just committed today - I decided to fix the typo here as well, fyi @siegfriedweber