ChRIS_ultron_backEnd
ChRIS_ultron_backEnd copied to clipboard
K8s: Enforce deployment ordering
Background
The backend services exhibit inter-dependencies, which need to be respected during deployment. Services polling other services and accessing databases should be started only once their dependencies are ready. This requirement is currently met through the depends_on
field within the docker-compose
file.
Issue The current Kubernetes deployment starts all service containers simultaneously, which frequently leads to failures in upstream services.
Task In case of inter-dependent services, a correct startup ordering should be enforced in order to prevent unhandled service failures and boost startup efficiency.
Notes Kubernetes-native ways to handle deployment sequencing include
- container probes (concept, configuration),
- init containers (concept, configuration).
Hi, I am interested in this issue.