8000 fix: adding docs about Keycloak CR security by shawkins · Pull Request #40260 · keycloak/keycloak · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fix: adding docs about Keycloak CR security #40260

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jun 6, 2025
Merged

fix: adding docs about Keycloak CR security #40260

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/guides/operator/basic-deployment.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -296,4 +296,15 @@ kubectl get secret example-kc-initial-admin -o jsonpath='{.data.password}' | bas

You can use those credentials to access the Admin Console or the Admin REST API.

=== Security Considerations

[WARNING]
====
Anyone with the ability to create or edit a Keycloak CR should be a namespace level admin.
====

Setting the Keycloak CR image requires a high degree of trust as whatever image is running will have access to any Secrets used for environement variables.

Similarly the unsupported podTemplate gives the ability to deploy alternative workloads which may be granted the same permissions as the operator itself - which includes the ability to access Secrets in the namespace.

</@tmpl.guide>
0