+1 for something like this but for older deployments I figured the OIDC
.wellknown endpoint was a decent indicator of availability.
However, deploys to Kuberbetes and AWS ECS still seem to get a bit wonky
for a minute or two while Infinispan establishes a new cluster state.
On Sat, May 20, 2017 at 9:44 AM Thomas Darimont <
thomas.darimont(a)googlemail.com> wrote:
Hello Hector,
there is already an issue for that in JIRA, see:
https://issues.jboss.org/browse/KEYCLOAK-1578
I played a bit with a new health endpoint SPI:
https://github.com/thomasdarimont/keycloak-health-checks
Cheers,
Thomas
2017-05-20 14:23 GMT+02:00 Hector Fernandez <hfernand(a)redhat.com>:
> Hi guys,
>
> We have a keycloak cluster setup in Openshift on which our healthchecks
> point to the endpoint `auth/version`. It would be nice if you provide an
> endpoint in your API that could tell us more info about healthiness or
> readiness of Keycloak (especially in a cluster mode).
>
> Do you have any similar endpoint?
> Otherwise, it could be a nice feature for envs such as Kubernetes
> --
> *<hector/>*
> --
> *<hector/>*
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev