Repository navigation
Replies: 1 comment
|
Okay, sorry my mistake. The Dockerfile is not necessarily required, because building the new keycloak-operator with maven automatically creates the Docker image. |
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.
Uh oh!
There was an error while loading. Please reload this page.
Hi
I created the following issue #14183 (enhancement). So far, there have been no discussions in this issue.
In our environment we want to set the "--override=true" for the KeycloakRealmImportJob, because we always want to override the realm-settings which are configured in the KeycloakRealmImport CR (the config/realm should always be overwritten, so that the config is guaranteed to match the CR). We also do not have any users in our database, as they are retrieved via an external IdentityProvider.
In order to implement this we adapt the following code line (https://github.com/keycloak/keycloak/blob/19.0.1/operator/src/main/java/org/keycloak/operator/controllers/KeycloakRealmImportJob.java#L164) to "--override=true" and build the keycloak operator by ourselves.
At the moment we can't find any example of the Dockerfile for the new keycloak-operator inside the operator directory (https://github.com/keycloak/keycloak/tree/main/operator), to create our customized docker image. Could someone provide any example like there is one for keycloak (https://github.com/keycloak/keycloak/blob/main/quarkus/container/Dockerfile)?
By the way, there is also a Dockerfile for the legacy Keycloak-Operator: https://github.com/keycloak/keycloak-operator/blob/main/Dockerfile.
All reactions