Repository navigation
Install custom themes with Quarkus on k8s #11846
Replies: 6 comments 11 replies
|
Hi @hausanstreicha ! Thanks for reaching out! Here we actually removed the support for extensions because we consider that mechanism not well suited for production environments. By contrast, we encourage building custom Docker images, and here we properly documented the process. Do you have any compelling use case where building a custom docker image is not viable/convenient? |
|
@andreaTP a compelling use case i found: a new image is always treated like a major deployment by keycloak operator (i.e. drain cluster to 1 node, run migration, scale up again). if i wanted to make a minor/patch release - or even changing a pixel in the theme(!) - using that approach, it turns that into a major release operation, which is totally unnecessary IMO. |
|
Hi @andreaTP, thank you for your quick response and help! My main reason for using extensions was convenience and simplicity to be honest. I have another question regarding the migration and setting a relative path. Right now, I don't know, if this is a bug or missconfiguration on my side. I opened an issue here. Do you happen to have an idea? Thanks again for your help in advance! |
I see, I hope that the benefits of using immutable images and improving dramatically startup time outweigh the convenience. Regarding the issue, I answered there already 🙂 👍 thanks for filing it! |
|
I just saw the comment on the https://www.keycloak.org/operator/customizing-keycloak:
So what is the recommended way to be able to use an extension like the metrics extension and a custom theme like in the example here https://www.keycloak.org/server/containers "Building your optimized Keycloak docker image", while still being able to use the server settings options from the new Kubernetes Keycloak CRD (spec.serverConfiguration)? |
the sentence refers to the fact that you won't be able to use "build options" as they are going to be ignored but you can freely use normal configurations. |
|
Thanks for clarifying that |
|
Hi, If I build a custom image, how do I get OLM installed operator to use it? |
|
I'm a bit confused here, with OLM and standard catalogs installed you should not need steps 3/4 (assuming the resources are self explanatory from the file names). Are you sure that you are not installing instead the old operator? Can you share the logs of the operator and the operator docker image used? |
|
Edit, sorry I'm from the phone, something is not correct in the setup, and the new keycloak CRD version is v2alpha1 |
|
Ok, makes sense, I am running the install from https://operatorhub.io/operator/keycloak-operator/candidate/keycloak-operator.v20.0.0-alpha.2. However, am getting an error when trying to apply the Keycloak CRD, it cannot find the secret: I thought the operator creates the secret based on the name passed to the keycloak CRD, is this not correct? |
|
No, the secret should be provided by the user https://www.keycloak.org/operator/basic-deployment |
|
Perfect, thank you |
|
hi everyone, I'm using the vanilla kubernetes installation of keycloak-operator and I'm still confused about how to select a custom theme as default with the operator. I build the custom image, added to the keycloak CR, it deploys the right image, but not sure how do I select my theme to be loaded as default. |
|
I kinda found the answer here. |
Uh oh!
There was an error while loading. Please reload this page.
Hi, I would like to switch from WildFly to Quarkus, but right now I don't know what's the best way to install custom themes, besides building your own docker image.
With WildFly you were able to set extensions in the custom resource (as shown here). I'm not able to find a similar solution for Quarkus.
Is there some documentation I missed to install custom themes with Quarkus on k8s?
Thanks for your help in advance!
All reactions