Why it exists
PACKAGE-FIRST RUNTIME
Published profiles need one reusable execution layer instead of reimplementing runtime behavior inside every package.
SOURCE SPLIT
Public scenario source content should evolve independently from the Infra engine bundle.
Productive K3S Infra provides the execution layer: package-first runtime around Productive K3S Core.
Keep Productive K3S Core as the bootstrap contract
Execute self-contained profile artifacts instead of source trees
Keep source-content ownership outside the engine
Runtime coverage
- Published profile artifacts from catalog or direct TGZ
- Local overrides passed by the invoking machine
- Runtime state restored across install, status, plan, and destroy
- Productive K3S Core bundles from a local checkout or a published release
Design principles
- Package-first: the public runtime interface operates on profile artifacts, not source trees
- Keep source ownership separate: public scenarios live in Productive K3S Profiles, not inside the engine
- Preserve state: status, plan, destroy, and addon flows should share one runtime view
Supported runtime inputs
- Published profile artifacts from catalog or direct TGZ
- Local override env files supplied by the invoking machine
- Runtime state restored across repeated profile commands
- Productive K3S Core bundles from local or remote releases
What it is not
- Not a replacement for Productive K3S Core
- Not the source-of-truth repo for public scenarios
- Not a promise that a packaged profile removes the need for local install-specific inputs
It is the package execution layer around Productive K3S profiles and Productive K3S Core.