Service that is responsible for pod count quota enforcement. Admiral communicates with
this service with messages like: “Can I start new pod” and
“I’m going to stop pod, forget about it”. In case this service disagrees, pod
is not started/stopped. The service stores it’s state in the MongoDB.
Default version always responds with yes and stores nothing. It is possible to
configure otherwise.
very bad
The downtime means Flow step pods starts and stops will be blocked. Due to retries it’s acceptable to stop service for no more then 5 minutes. After 5 minutes all Flows that have pods starting, will be suspended.
Scalable to any reasonable amount of pods.
Use rolling release. Delete pod and create new. It’s forbidden to have less then one active pod.
None in the default configuration.