Why it exists
CURATED PATHS
Teams want ready-to-use solution paths instead of rebuilding the same deployment decisions every time.
SEPARATE LAYERS
The solutions should evolve without forcing the deployment engine and the base installation layer to absorb all the change.
Productive K3S Profiles is the curated solution layer in the ecosystem.
Keep Core as the base installation contract
Keep Infra as the orchestration engine
Let curated solution paths evolve on their own cadence
Recommended paths
- On-prem basic: deploy over existing hosts reachable through SSH
- AWS single-node: evaluate a simple cloud path on EC2
- Multipass: validate a local multi-node path before going further
- ARM path: keep an explicit public route for smaller ARM targets
Design principles
- Curated over ad hoc: publish solution paths that feel ready to use, not disconnected fragments
- Keep orchestration separate: Infra executes the solutions, but does not own the solution catalog
- Keep the contracts visible: defaults, helper scripts, and packaging metadata should remain reviewable
How it fits
- Start here when you want to choose a curated solution path
- Continue to Infra when you want that path executed on a platform
- Continue to CLI when you want the simplest and recommended operator interface
- Remember that this repository owns the solution definitions, not the deployment engine
What it is not
- Not the deployment engine
- Not the base Kubernetes installation layer
- Not a claim that every public path is already the final form for every production need
It is the curated solution layer for Productive K3S deployments.