The current health check for instance deployments requires manual intervention by pressing a button to make a request to the deployment_url. This is not very efficient and reliable, as it depends on the availability and performance of the deployment_url having to go through external sources.
A better solution would be to automate the health check to run periodically (every n seconds or minutes) using the container names of the instances. This would require creating another service that runs within the deployment network (currently IRIS) and can access the container through container names. This way, the health check would not need any auth_header or other checks, and would be more accurate and consistent.
Feel free to comment and propose any changes or additions you think are necessary.
Tasks:
The current health check for instance deployments requires manual intervention by pressing a button to make a request to the deployment_url. This is not very efficient and reliable, as it depends on the availability and performance of the deployment_url having to go through external sources.
A better solution would be to automate the health check to run periodically (every n seconds or minutes) using the container names of the instances. This would require creating another service that runs within the deployment network (currently IRIS) and can access the container through container names. This way, the health check would not need any auth_header or other checks, and would be more accurate and consistent.
Feel free to comment and propose any changes or additions you think are necessary.
Tasks: