Repository navigation
Issue with Reflecting Theme Data Changes in Keycloak Without Pod Restart #35371
Unanswered
nitindhiman314e
asked this question in
Q&A
Replies: 1 comment
|
The Keycloak operator will in version 26.2 support rolling updates for changed images where only the theme has changed. See #36305 (comment) for details. In your setup, I would usually recommend a custom built Keycloak image which includes the theme instead of a PVC to utilize that functionality we added for the upcoming 26.2 release. |
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.
Description
We are using Keycloak in a Kubernetes (K8s) setup, where the Keycloak instance is managed by the Keycloak operator. We are also utilizing custom themes, which are stored in a persistent volume claim (PVC). However, we are encountering an issue where changes made to the theme data are not reflected in Keycloak until the pod is manually restarted. This behavior disrupts the continuous deployment process, as changes to themes require a pod restart to take effect.
We would like to explore solutions to apply rolling updates or a blue-green deployment strategy to ensure that theme data changes are automatically reflected without requiring a pod restart. Please suggest.
All reactions