Currently the health checks runs against the concerto API (curl call). If the API is disabled in the site configuration, the health check fails.
If the container is not healthy could lead to be taken offline by traefik, even if is healthy.
Actual behavior
The health check must not be running and depend on the API functionality to be on. If that is the case, the admin user must not be allowed to turn off the API.
Steps to reproduce the issue
1.- Build a stack as follow:
traefik -> concerto.
2.- Disable the API on administration->settings
3.-Traefik will drop the connection: "Filtering unhealthy or starting container".
Concerto Platform version
Docker tag 5.0.26
Expected behavior
Currently the health checks runs against the concerto API (curl call). If the API is disabled in the site configuration, the health check fails. If the container is not healthy could lead to be taken offline by traefik, even if is healthy.
Actual behavior
The health check must not be running and depend on the API functionality to be on. If that is the case, the admin user must not be allowed to turn off the API.
Steps to reproduce the issue
1.- Build a stack as follow:
traefik -> concerto.
2.- Disable the API on administration->settings
3.-Traefik will drop the connection: "Filtering unhealthy or starting container".