Configurable workload health checks

[krucod3]

Description

What a running workload means is a matter of interpretation and is very specific to the use-case and the workload. For some use-cases a basic container is running is enough (current behavior), for others a readiness of the application(s) running in a container is needed. On the other hand not all applications and workloads support or can be changed to support an active readiness polling or pushing.

To support all use-cases we shall extend Ankaios to support per workload health check configurations. If no specific configuration is set, the default (current) behavior is used.

Note: It is also very important to define when a workload is stopped. If we need to wait for one workload to be stopped before we can stop another one (e.g. to allow the first to write data to the second), it is important to properly mark the stopped state too.

Goals

Extend Ankaios with a configurable per workload health check support.

Final result

Summary

To be filled when the final solution is sketched.

Tasks

Initial task list

• [ ] define which health checks are supported by Ankaios
• [ ] define how check intervals are configured
• [ ] define the configuration format
• [ ] ...