Readiness probe failed about helm-charts

[KaiWedekind]

What solved my problem was setting fsGroup to zero in securityContext:

securityContext:
    runAsUser: 1000
    fsGroup: 0
    runAsNonRoot: true

Keycloak was not able to create folders with fsGroup: 1000 (jboss), it had to be 0 (root).

drwxrwxr-x 11 jboss root  4096 May 12 00:21 keycloak

[unguiculus]

Can you share some more details on your environment? Do you use Istio by any chance? See #24.

[RAbraham]

I'm having the same issue. @KaiWedekind 's solution unfortunately didn't work in my context. I'm testing it locally on MacOS. The only change I made was to point to an existing postgres local instance. Is this issue caused if the database keycloak is an empty database? Does the keycloak deployment try to populate an empty database with keycloak specific schemas?

[KaiWedekind]

I use Istio, indeed. My issue wasn't initializing iptables though, my keycloak container just Could not create directory for root '/opt/jboss/keycloak/standalone/tmp/vfs/temp' as included in the log snapshot.

[unguiculus]

Should be fixed by #25.