Skip to main content
Version: next

Validated Deployments

Choose a tested baseline by lane, then adapt it without forgetting what was actually proven.

This section is for teams that want a known-good starting point instead of assembling a topology from scratch. Each validated lane pairs a reference architecture with the deployment recipe that reproduces it. Generic operator setup, backup, and restore guidance still lives in the main docs.

Choose a validated baseline

  1. 01

    Cloud baselines

    Start here when you want the Amazon EKS development or hardened lanes and need the architecture and recipe kept together.

    Open
  2. 02

    Local baselines

    Use the k3d lanes for workstation validation, hardened rehearsal, and cross-cluster DR practice without treating them as generic production blueprints.

    Open
  3. 03

    Cross-cluster DR lane

    Go directly to the validated DR architecture when the goal is restore rehearsal, shared Transit, and snapshot cutover proof.

    Open
Validated lane pages are not the canonical operator runbooks

The main operator guides remain the source of truth for install, backup, restore, upgrade, and recovery behavior. This section proves specific environment shapes and links to the exact lane that was exercised.

After you choose a baseline

Next release documentation

You are reading the unreleased main docs. Use the version menu for the newest published release, or check the release notes for what is already out.

Was this page helpful?

Use Needs work to open a structured GitHub issue for this page. The Yes button only acknowledges the signal locally.