Repository navigation
Future of declarative configuration in Keycloak #50888
dominikschlosser
started this conversation in
Ideas
Replies: 1 comment
|
One of the Keycloak teams is working to provide a Client CR. Once that exists, other entities might follow. Follow #43297 for the progress. See the parent issue work work already completed. There are already people from the Keycloak team and the community involved, adding more people will not necessarily make it faster. Still, maybe you can give it a test run and provide feedback to the team. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello dear Keycloak-team (especially @ahus1 ) and community,
Keycloak 26.7.0 has made great improvements to operate Keycloak in a way i would call "cloud native": Stateless without the need for distributed caches and support for declarative client configuration in the operator.
We run Keycloak in a similar fashion in production (10M users, 1M logins/day, multiple deployments per day without downtime) for multiple years now by heavily customizing Keycloaks storage: A fork of an earlier Keycloak-experiment (filestore) for config-like data (realms, clients, scopes, idps, groups, roles) and a database for dynamic data (users, sessions, singleuseobjects, ...).
This enables version-controlled production changes without ever touching the Admin API or GUI and without ever having to fear problems with syncing config to the database (as we had early when using the keycloak-config-cli community project).
Right now we are thinking about migrating from file-based config storage to one that uses K8s custom resources directly.
There are now multiple ways to run Keycloak in a similar "cloud native" way and i documented them (each with a working demo) here: https://github.com/dominikschlosser/cloud-native-keycloak
I would like to hear your thoughts about this. Is Keycloak ever going to separate "config" from "dynamic data" and support stuff like this out-of-the-box? What do you think about those community efforts? Are you willing to, for example, accept PRs that makes community projects like this easier / removes roadblocks (for example the DatastoreProviderSPI thankfully still exists, but new features like organizations are not added there)?
Thank you!
All reactions