Philipp B.
Philipp B.
Are there any news on this? Even creating a generous role with ``` spec: allow: impersonate: roles: - '*' users: - '*' kubernetes_groups: - '*' kubernetes_users: - '*' ``` does...
Upgrading to the newest major version seems to do the trick :)
Similar experience here. Oddly enough, killing the Pod multiple times still managed to get it running 🤷♂️
Related issue: https://github.com/bitnami/charts/issues/11067 Custom values are basically a must. But related to postgres we only have ``` postgresql: enabled: true image: tag: 11.14.0-debian-10-r28 persistence: existingClaim: data-keycloak-postgresql-0 ``` which is working...
Yep. Just tried deploying r5 while toggling `KEYCLOAK_PRODUCTION`. With `KEYCLOAK_PRODUCTION` set to `true`, I get the `No suitable driver found error` and Keycloak fails to start. If I set it...
Ping @alemorcuq
@alemorcuq I can look into it. But my approach would be identical to https://github.com/bitnami/bitnami-docker-keycloak/pull/91 so i'd basically just massage @rpiecyk's PR to work with this repo.
On the same level as ``datasources: []`` you can also define a ```deleteDatasources: []```.
It does. Exactly as I had described above. No manual configMap editing needed.
Opened a PR for it.