-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Open
Labels
Description
Name and Version
bitnami/keycloak 25.3.0
What is the problem this feature will solve?
The current Bitnami Keycloak Helm chart uses generic health check paths (TCP socket). Keycloak officially provides specific endpoints for liveness (/health/live), readiness (/health/ready), and startup (/health/started) probes. The chart not using these by default creates a discrepancy with standard Keycloak best practices and requires manual configuration for optimal Kubernetes health monitoring.
What is the feature you are proposing to solve the problem?
Update the Bitnami Keycloak Helm chart to use Keycloak's official /health/live, /health/ready, and /health/started endpoints for its liveness, readiness, and startup probes by default.
What alternatives have you considered?
No response