# ATM10 runtime and recovery

Argo CD deploys the stock Java 21 runtime directly from
`deployment.yaml`. The existing modpack tree, including libraries, mods,
configs, worlds, and map data, stays at `/home/feedc0de/ATM10` on arschrock.
The pod runs as UID/GID 1000, one replica, `Recreate`, with no resource limits.

For maintenance or rollback, change the Deployment replicas to zero in GitOps
and wait until the pod is gone before starting byobu against that same data
directory. To return to Kubernetes, stop byobu completely, restore replicas to
one, and wait for Argo CD and the Java status metric to become healthy. Never
let the host process and pod write the directory simultaneously.

The normal LoadBalancer address is dynamically assigned; the separate direct
service also answers on `10.12.4.170` and `192.168.0.2`.