Repository navigation
Replies: 2 comments 1 reply
|
hmm maybe this is related, I will see: keycloak/keycloak-operator#430 |
|
still no clue - I added these envs to keycloak resource and also to operator deployment - in both cases nothing - I tried even to remove Keycloak resource and add it again - nothing, it wasn't even recreated |
|
Well, I have no idea how it should work properly using keykloak operator and a keycloak resource - I cannot force it in any way. I just updated operator to use latest version of image and I added to it env vars like RELATED_IMAGE_KEYCLOAK and RELATED_IMAGE_KEYCLOAK_INIT_CONTAINER pointing to new base images for keycloak. After it I needed to modify images' versions in StatefulSet (which is managed by the operator in fact) by myself. And then naturally keycloak instance was updated properly. But I think the idea of an operator and related CRDs is different and it should be tackled it in more elegant way? |
Uh oh!
There was an error while loading. Please reload this page.
I used legacy operator in version 18.0.0 and later 18.0.2 update came up - how can I enforce the existing keycloak cluster (created with help of keycloak CRD) to update itself? I understand I should update the operator first but what next? how to enforce keycloak recreation using new images with 18.0.2 image tag instead of 18.0.0 to apply automatic update process ?
All reactions