GitOps strategy using the keycloak operator

[shaneboulden]

Hey everyone, I recently tried to implement a GitOps strategy using the KC operator.

My realm import works great - the realm is created with the correct groups and users. But, additional groups added to the KeycloakRealmImport CR aren't reconciled, and it looks like creating the KeycloakRealmImport CR is a one-shot event.

Is there any work in progress to support realm reconciliation, via the operator, that would support a GitOps strategy for KC management?

Or, any other thoughts on KC and GitOps?

[shawkins]

it looks like creating the KeycloakRealmImport CR is a one-shot event

That is currently correct.

There is no good workaround because the import job logic is set to --override=false.

So even if you delete the import after the job completes, and create an updated CR later, it won't overwrite the existing one.

We're looking to address this eventually with the Admin Api V2 work. In the meantime you could open an enahancement to have the import optionally preform an overwrite - but keep in mind that fully deletes the realm before importing the new one.