Validated Deployments / Local Baselines

Use local lanes for rehearsal, validation, and DR proof, not as accidental production defaults.

The local validated scope comes from the project's k3d environment. These lanes are valuable because they prove concrete behaviors such as hardened bootstrap, passthrough access, ACME issuance, and cross-cluster restore. They are not a substitute for making an explicit production platform choice.

Open k3d DevelopmentOpen k3d Cross-Cluster DR

Use local baselines when you need to

• rehearse a development or hardened lane on workstation-grade infrastructure
• prove a boundary such as external TLS passthrough, internal ACME, or shared Transit unseal
• practice restore and cutover behavior in the validated cross-cluster DR lane

Validated local lanes

1. 01

   k3d Development

   Shared terminating edge, RustFS backups, JWT bootstrap, and a development-profile lane for rehearsal and integration work.

   Open lane
2. 02

   k3d Hardened / External TLS

   Transit auto-unseal, external TLS Secrets, and user-managed passthrough for the closest local analogue to a hardened external-certificate deployment.

   Open lane
3. 03

   k3d Hardened / ACME

   Transit auto-unseal with OpenBao-managed ACME and validated hostname resolution in the local hardened ACME lane.

   Open lane
4. 04

   k3d Cross-Cluster DR

   A proving lane for shared Transit, shared snapshot storage, and restore rehearsal across separate source and target clusters.

   Open lane

Only the DR restore runbook stays lane-specific here

Generic backup and restore procedures belong in the main Operate docs. The cross-cluster DR restore procedure remains in this section because it depends on the exact validated DR lane assumptions.

Related catalogs

Local recipe catalogBrowse the local deployment procedures directly if you already know which lane you want to reproduce.Generic restore guideUse the main restore docs for the canonical workflow outside the specific DR proving lane.