Validated Deployments / Local Baselines

Validated local baselines

Validated k3d baselines are listed here for development, hardened rehearsal, and cross-cluster DR.

Open k3d DevelopmentOpen k3d Cross-Cluster DR

Use local baselines to

• rehearse a development or hardened lane on workstation-grade infrastructure
• exercise 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

   Development profile with shared terminating edge, RustFS backups, and JWT bootstrap for rehearsal and integration work.

   Open lane
2. 02

   k3d Hardened / External TLS

   Hardened external-certificate baseline with Transit auto-unseal, external TLS Secrets, and user-managed passthrough.

   Open lane
3. 03

   k3d Hardened / ACME

   Hardened ACME baseline with Transit auto-unseal, OpenBao-managed ACME, and local hostname resolution.

   Open lane
4. 04

   k3d Cross-Cluster DR

   Cross-cluster DR baseline with shared Transit, shared snapshot storage, and restore rehearsal across source and target clusters.

   Open lane

Lane-specific runbook scope

Generic backup and restore procedures belong in the main Operate docs. The cross-cluster DR restore procedure stays here because it depends on the DR-lane assumptions used in this catalog.

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.