Details
-
Epic
-
Resolution: Obsolete
-
Major
-
None
-
None
-
Healthcheck
-
NEW
-
NEW
Description
Motivation
Currently, Keycloak Server doesn't provide a Healthcheck Endpoint, which could be used by Kubernetes. Instead, we use custom CLI or HTTP calls against the Management URI and check multiple things manually. The ultimate solution is to provide this kind of functionality directly in the Keycloak Server.
Design
https://github.com/keycloak/keycloak-community/pull/55
Risks/Limitations
The implementation should be reviewed by the Integreately Team.
Rough Estimate
1 sprint for 1 person for the Server implementation
1 week for 1 person for Keycloak Container and Keycloak Operator
Open Questions
None.
Attachments
Issue Links
- is blocked by
-
KEYCLOAK-12399 Keycloak container should crash on unrecoverable error
-
- Closed
-
- is duplicated by
-
KEYCLOAK-13646 Reimplement Readiness and Liveness Probes in Keycloak Operator
-
- Closed
-
- is related to
-
WFLY-13931 Allow defining HealthChecks without CDI
-
- Open
-
-
KEYCLOAK-13244 Readiness check failing for longer than needed during external DB downtime
-
- Closed
-
- relates to
-
KEYCLOAK-8288 Observability
-
- Plan
-
-
KEYCLOAK-13703 Multiple errors: readiness and shutdown checks
-
- Closed
-
- links to