[ 
https://issues.apache.org/jira/browse/IGNITE-27352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vadim Pakhnushev updated IGNITE-27352:
--------------------------------------
    Description: 
In order to enable proper k8s deployments we need to have liveness and 
readiness 
[probes|https://kubernetes.io/docs/concepts/configuration/liveness-readiness-startup-probes/].
Liveness probe {{/health/liveness}} should always return 200 OK as long as the 
REST is available. We can revisit this later and add additional liveness 
indicators.
Readiness probe {{/health/readiness}} should return 200 OK when node has joined 
the logical topology and 503 Service Unavailable when node hasn't yet joined 
the cluster.

  was:
In order to enable proper k8s deployments we need to have liveness and 
readiness 
[probes|https://kubernetes.io/docs/concepts/configuration/liveness-readiness-startup-probes/].
Liveness probe should always return 200 OK as long as the REST is available. We 
can revisit this later and add additional liveness indicators.
Readiness probe should return 200 OK when node has joined the logical topology 
and 503 Service Unavailable when node hasn't yet joined the cluster.


> Create health probe endpoints
> -----------------------------
>
>                 Key: IGNITE-27352
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27352
>             Project: Ignite
>          Issue Type: Improvement
>          Components: rest ai3
>            Reporter: Vadim Pakhnushev
>            Assignee: Vadim Pakhnushev
>            Priority: Major
>              Labels: ignite-3
>
> In order to enable proper k8s deployments we need to have liveness and 
> readiness 
> [probes|https://kubernetes.io/docs/concepts/configuration/liveness-readiness-startup-probes/].
> Liveness probe {{/health/liveness}} should always return 200 OK as long as 
> the REST is available. We can revisit this later and add additional liveness 
> indicators.
> Readiness probe {{/health/readiness}} should return 200 OK when node has 
> joined the logical topology and 503 Service Unavailable when node hasn't yet 
> joined the cluster.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to