Repository navigation
Declarative realm lifecycle management in the Keycloak Operator #53589
federicolepera
started this conversation in
Ideas
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.
Hi Keycloak maintainers and community,
I would like to discuss extending the existing Keycloak Operator to manage Keycloak realms declaratively.
My goal is to make realm management straightforward in a GitOps workflow: define a realm in a Kubernetes resource, keep that definition in Git, and have the operator reconcile the realm's lifecycle with the desired state. This would include creating a realm, reporting its status, applying supported changes, and handling deletion safely.
The existing KeycloakRealmImport resource is useful for importing a realm, but I am looking for ongoing lifecycle management rather than a one-time import.
As a first step, I would propose a narrowly scoped realm resource and reconciliation behavior. More advanced identity-platform features could be discussed separately; they are not a prerequisite for this proposal.
Before working on an implementation, I would appreciate your feedback on:
If this direction is appropriate, I would be happy to refine the scope and work on an initial contribution.
All reactions
Replies: 0 comments