Bootstrap: Full Mode
Audience
This page is for operators and maintainers who need a production-oriented bootstrap flow closer to the formal runtime shape.Goal and Scope
This page explains the full-mode bootstrap flow and why it is closer to the final runtime baseline.Core Concepts
- full mode still begins with the binary bootstrap entry
- the goal is to move the control plane and dependencies into K3s image-based runtime as early as possible
- environment, approval, audit, and persistence expectations are closer to formal production
Standard Workflow
- complete preflight and source selection
- install or adopt K3s
- deploy PostgreSQL, object storage, pooler, and other core dependencies
- deploy the control-plane services
- initialize environments, quotas, policies, and default security baselines
CLI Examples
Web UI Path
Choose full mode in the install wizard and continue through the more complete bootstrap flow.Pitfalls / Risk Notes
- full mode is closer to the formal runtime, but it is not a different runtime model
- if key state is still backed by in-memory stubs, full mode still does not meet the final runtime goal