Dear Community Members,
Has anyone recently tested a Keycloak setup in a cloud-native Kubernetes environment using Helm charts?
I’m facing an issue where the admin console takes a long time to load, and there’s no further response when Keycloak is installed with ingress enabled.
I’ve tried different approaches, and below are the values from my latest Helm chart configuration. If anyone has successfully completed the installation, could you share your experience and suggest what might be causing the issue in the values file below?
helm install keycloak bitnami/keycloak --version 24.4.9 -n keycloak --create-namespace -f keycloakUserValues.yaml --set image.repository=bitnamilegacy/keycloak --set postgresql.image.repository=bitnamilegacy/postgresql --set global.security.allowInsecureImages=true
############################
Keycloak – AKS Baseline values file
############################
replicaCount: 1
############################
Admin Credentials
############################
auth:
adminUser: admin
adminPassword: admin123 # change in production
############################
Production & Proxy
############################
production: true
proxy: edge
httpRelativePath: “/”
############################
Service (Internal only)
############################
service:
type: ClusterIP
ports:
http: 80
############################
Ingress
############################
ingress:
enabled: false
############################
Proxy / Header Handling
############################
extraEnvVars:
- name: KC_HTTP_ENABLED
value: “true” - name: KC_PROXY_HEADERS
value: “xforwarded” - name: KC_HOSTNAME_STRICT
value: “false” - name: KC_HOSTNAME_STRICT_HTTPS
value: “false”
############################
Database (PostgreSQL)
############################
postgresql:
enabled: true
auth:
username: bn_keycloak
password: bn_keycloak
database: bitnami_keycloak
############################
Global PostgreSQL (installed from Bitnami)
############################
global:
postgresql:
auth:
username: bn_keycloak
password: bn_keycloak
database: bitnami_keycloak
############################
Probes
############################
livenessProbe:
enabled: true
initialDelaySeconds: 180
periodSeconds: 10
timeoutSeconds: 5
failureThreshold: 6
readinessProbe:
enabled: true
initialDelaySeconds: 60
periodSeconds: 10
timeoutSeconds: 5
failureThreshold: 6
############################
Resources
############################
resources:
requests:
cpu: 500m
memory: 512Mi
limits:
cpu: 1000m
memory: 1024Mi