200 fix hardcoding pieces in helm chart #669
Conversation
robkooper
left a comment
robkooper
left a comment
There was a problem hiding this comment.
This will hard-code the realm to be for a specific instance, and will overwrite the changes that the user makes on a restart of keycloak.
There was a problem hiding this comment.
This is a massive file, and not sure all the parameters are needed if they are the defaults.
There was a problem hiding this comment.
there is a mini version of that but i haven't test it
Ah right... what's a better way then, using initContainers? |
|
I would have it as an optional hook (post-install) in the helm chart when you install it (not upgrade). I would have a boolean flag that is "install realm" and have it be false. This way the user can decide that you want to import it. Problem with init is that if you are not careful it will overwrite any changes the user has made. |
|
I would check to see how you can make it such that you can use some template variables and have the host for ingress be injected in the json document for the realm, as well as minimize it as much as possible. |
|
Created a new task for it #689 for the future. |
Load the keycloak realm in as ConfigMap. You can test by deleting the Realm in keycloak and then restart the keycloak pods see if it gets loaded correctly.