Neon Law | Workshops | Deploy The Navigator | Step

The Navigator deployment matrix

Each deployment has one config.toml and one encrypted secrets.enc.yaml under the operator-managed deployment root: $NAVIGATOR_DEPLOYMENTS_DIR/deployments/<row>/. The config supplies that row's project, region, cluster, namespace, host, and image settings. Keep each row's database, buckets, Kubernetes namespace, runtime identity, and Secret isolated from other rows. The private root is supplied by the operator and is not part of this source repository.

Presenter notes

The runtime topology is defined by the operator's rows. A staging row can exercise sample matters through the same shared application, data-access, authorization, API, and agent-protocol code used by production brands. An image registry project is a separate publishing resource, not an application environment.

Read the deployment matrix from the private operator configuration. A row's hostname is configuration, not code — NAVIGATOR_PUBLIC_HOST in its config.toml — so the public URL can change without renaming a crate, image, or deployment. Keep each production brand's resource prefix, database, cluster, namespace, runtime identity, Secret, and Restate journal isolated. Staging proves the common application; brand route tests prove the public face shipped by each immutable image.

View all slides Open display