A custom process to spawn next to the nodes: its command, args, env,
image (provider specific), named ports, resources (provider
specific), and its lifecycle: ready_check, depends_on, one_shot and
timeout.
Another custom process this one starts after. Written as a bare name
("postgres") or as { name = "init", condition = "..." }; without a
condition the target’s natural one applies, see
CustomProcess::natural_condition.
How a custom process is known to be ready. tcp is a declared port name
that must accept a connection; http is a declared port name and a path
that must answer 2xx. On kubernetes the check is the pod’s readiness
probe; elsewhere zombienet probes the port from where it runs. How long
to wait is the process’s timeout.
Where a custom process is in its lifecycle. In zombie.json it is the
state field (starting, ready, completed, failed) plus
state_reason for a failure; a record without one is taken as ready.