Deployment

Purpose

One runbook per environment - deliberately separate pages, not toggles on one page, so staging and production never look like interchangeable variants of the same command.

Pages in this section

• Local - your own machine's k3d cluster.
• Staging - the real pre-production cluster, deployed automatically by Jenkins on every release tag.
• Production - deployed only via Jenkins' manual approval gate. No production deployment is executed as part of this documentation portal.
• Release Checklist - the full precondition list before cutting a release tag.

Shared shape

Every runbook in this section follows: Preconditions → Backup/checkpoint → Build → Deploy → Database migration → Verification → Smoke testing → Monitoring → Rollback - so the steps are predictable even though the targets (and their risk level) are completely different.

Which environment am I looking at?

	Local	Staging	Production
Cluster	your own k3d	real, shared K3s node	same node, separate namespace
Deployed by	you, manually	Jenkins, automatically, on a release tag	Jenkins, with a human approval gate
Data	disposable, local-only	real test data	real customer data
This portal executes deploys here?	Only what you explicitly run yourself	No	Never