The applier is a host process, not a container
Everything that actually submits an application runs as forever_apply_scheduler.py on the MAIN host. None of the containers further down this page apply to anything, so a healthy fleet says nothing about whether the engine is running. This panel is the engine; the fleet is the furniture around it.
Loading the containers snapshot.
Where this fleet data came from
Named in full, including its own heartbeat and last errorContainers by host
This engine first, then the other stacks sharing the machine — read-only: this page has no control path over anything listedLoading the fleet snapshot…