Why it exists
COMPLETE DEPLOYMENTS
Users need a coherent way to deploy complete solutions without assembling each platform path by hand.
REUSABLE ORCHESTRATION
The deployment layer should stay reusable while the curated solutions keep evolving in their own repository.
Productive K3S Infra is the reusable orchestration layer above Core.
Keep Core responsible for the base installation contract
Execute curated deployment solutions consistently
Keep solution definitions in Profiles instead of mixing them into the engine
How it fits
- Use Infra directly when you want explicit control of the deployment layer
- Use Profiles to choose the curated solution path you want to deploy
- Use Productive K3S CLI when you want the simplest and recommended unified experience
- Let Core keep ownership of the base Kubernetes installation underneath
Design principles
- Solution-first: lead with complete deployment paths, not with internal mechanics
- Keep the layers separate: Profiles owns curated solutions, Core owns base installation, Infra owns orchestration
- Preserve one runtime view: status, plan, destroy, and related flows should share coherent runtime state
What it works with
- Curated deployment solutions defined in Productive K3S Profiles
- Local or remote Productive K3S Core bundle sources
- Runtime state reused across repeated deployment commands
- CLI-driven or direct operator usage depending on the workflow you want
What it is not
- Not the base Kubernetes installation layer
- Not the source-of-truth catalog of curated deployment solutions
- Not the only way to operate the ecosystem
It is the deployment and orchestration layer in the Productive K3S path.