[
https://issues.apache.org/jira/browse/JAMES-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
hung updated JAMES-4070:
------------------------
Description:
*Why*
k8s consider a pod not healthy when receiving the response code >= 400.
James healthcheck response code:
200: All checks have answered with a Healthy or Degraded status. James services
can still be used.
503: At least one check have answered with a Unhealthy status
`degraded` with 200 code won't trigger k8s pod restart.
We should have an option to restart the k8s pod when `degraded` performance
*How*
We could add a flag as a query parameter to consider degraded as failed. EG
`GET 127.0.0.1:8000/healthcheck/checks/ImapCheck?strict`
Would return 503 response code if unhealthy and degraded
While
`GET 127.0.0.1:8000/healthcheck/checks/ImapCheck`
Would return 503 when unhealthy and 200 for degraded.
We would need to implement `GET 127.0.0.1:8000/healthcheck?strict` too.
was:
*Why*
k8s consider a pod not healthy when receiving the response code >= 400.
James healthcheck response code:
```
200: All checks have answered with a Healthy or Degraded status. James services
can still be used.
503: At least one check have answered with a Unhealthy status
```
`degraded` with 200 code won't trigger k8s pod restart.
We should have an option to restart the k8s pod when `degraded` performance
*How*
We could add a flag as a query parameter to consider degraded as failed. EG
`GET 127.0.0.1:8000/healthcheck/checks/ImapCheck?strict`
Would return 503 response code if unhealthy and degraded
While
`GET 127.0.0.1:8000/healthcheck/checks/ImapCheck`
Would return 503 when unhealthy and 200 for degraded.
We would need to implement `GET 127.0.0.1:8000/healthcheck?strict` too.
> Healthcheck: have a query param to return 503 code if degraded
> --------------------------------------------------------------
>
> Key: JAMES-4070
> URL: https://issues.apache.org/jira/browse/JAMES-4070
> Project: James Server
> Issue Type: Improvement
> Reporter: hung
> Priority: Major
>
> *Why*
> k8s consider a pod not healthy when receiving the response code >= 400.
> James healthcheck response code:
> 200: All checks have answered with a Healthy or Degraded status. James
> services can still be used.
> 503: At least one check have answered with a Unhealthy status
> `degraded` with 200 code won't trigger k8s pod restart.
> We should have an option to restart the k8s pod when `degraded` performance
> *How*
> We could add a flag as a query parameter to consider degraded as failed. EG
> `GET 127.0.0.1:8000/healthcheck/checks/ImapCheck?strict`
> Would return 503 response code if unhealthy and degraded
> While
> `GET 127.0.0.1:8000/healthcheck/checks/ImapCheck`
> Would return 503 when unhealthy and 200 for degraded.
> We would need to implement `GET 127.0.0.1:8000/healthcheck?strict` too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
