You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting up healthcheck there is a field called "Return Code", this suggests that it is possible to specify the expected response code of the path.
This is great I have multiple backends where paths are behind a middleware so they return 401 for the healtcheck pings. Saldy setting this field to 401 does not produce the desired outcome, the healtcheck will fail. More specificaly, the status will stuck in "Starting". As to my knowledge this is because the docker healtcheck does not get the correct return code.
I tried to check the codebase and I think the value of this field is not used anywhere, seemingly it was forgotten.
It would be great to have this feature :)
Minimal Reproduction (if possible, example repository)
Start a service that returns 401 on one of its route and enable healthcheck on this route with "Return Code" 401. Try to deploy the service.
Exception or Error
The container will be stuck in starting status.
Version
v4.0.0-beta.277
The text was updated successfully, but these errors were encountered:
By default this repo will return error code 401 with message "Unauthorized" and can be configured with environment variable ERROR_CODE and ERROR_MESSAGE
Description
When setting up healthcheck there is a field called "Return Code", this suggests that it is possible to specify the expected response code of the path.
This is great I have multiple backends where paths are behind a middleware so they return 401 for the healtcheck pings. Saldy setting this field to 401 does not produce the desired outcome, the healtcheck will fail. More specificaly, the status will stuck in "Starting". As to my knowledge this is because the docker healtcheck does not get the correct return code.
I tried to check the codebase and I think the value of this field is not used anywhere, seemingly it was forgotten.
It would be great to have this feature :)
Minimal Reproduction (if possible, example repository)
Start a service that returns 401 on one of its route and enable healthcheck on this route with "Return Code" 401. Try to deploy the service.
Exception or Error
The container will be stuck in starting status.
Version
v4.0.0-beta.277
The text was updated successfully, but these errors were encountered: