Why it exists
UNIFIED UX
Most users want one simple way to consume the ecosystem instead of learning each component interface separately.
REAL COMPONENTS
That simpler experience should still preserve the real Core and Infra contracts instead of reimplementing the platform inside the CLI.
Productive K3S CLI is the recommended UX layer above the independent ecosystem components.
Keep Core and Infra authoritative
Give users one recommended interface
Keep direct usage possible when deeper control matters
How to use it
- Use CLI when you want the simplest and recommended Productive K3S experience
- Use Core directly when you want the most explicit base installation contract
- Use Infra directly when you want explicit control over the deployment layer
- Keep the same CLI path across development and published releases
Design principles
- Delegate, do not duplicate: the CLI should route into Core and Infra, not absorb their implementation
- Recommended, not mandatory: the best normal path should stay simple without pretending the underlying components stopped existing
- Keep provenance visible: bundle resolution and component boundaries should remain understandable
Where it fits
- The recommended user-facing path across the ecosystem
- Operator workstations that need one coherent command surface
- Development setups that still benefit from a unified interface
- Cross-platform use on Linux, macOS, and Windows
What it is not
- Not a replacement for Productive K3S Core
- Not a replacement for Productive K3S Infra
- Not a reason to hide component boundaries
It is the simplest and recommended interface for using Productive K3S.