Skip to content

fix: requiring secrets to be labeled for use with client crs - #53129

Open
shawkins wants to merge 1 commit into
keycloak:mainfrom
shawkins:iss52320
Open

shawkins wants to merge 1 commit into
keycloak:mainfrom
shawkins:iss52320

Conversation

@shawkins

Copy link
Copy Markdown
Contributor

Adds a requirement that client cr secrets must be labeled.

The label was chosen to be general should we want to use the same convention with other resources - but I'm open to other suggestions.

closes: #52320

closes: keycloak#52320

Signed-off-by: Steve Hawkins <shawkins@redhat.com>

This comment was marked as outdated.

@shawkins
shawkins marked this pull request as ready for review September 23, 2026 22:12
@shawkins
shawkins requested review from a team as code owners September 23, 2026 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add v2 operator restrictions for referenced secrets

2 participants