Skip to content

CLI-Oriented Path

For users who want the simplest and recommended Productive K3S experience from the beginning:

  1. Start with productive-k3s-cli.
  2. Use the CLI documentation to understand which core and infra capabilities it is exposing for your workflow.
  3. Drop into productive-k3s-core, productive-k3s-infra, productive-k3s-profiles, or productive-k3s-addons only when you need component-level detail.

The CLI path is about a better normal UX, not about hiding the underlying repository boundaries.