Unified command line for Productive K3S

Productive K3S CLI

Productive K3S CLI provides one executable, `pk3s`, for working with Productive K3S Core and Productive K3S Infra through a consistent, release-aware command surface.

It resolves versioned bundles, validates their runtime contract, and delegates execution into the public Core and Infra entrypoints instead of reimplementing their logic.

View on GitHub Open README

Why it exists

SPLIT ENTRYPOINTS

Separate Core and Infra commands are accurate, but harder for users to discover and operate consistently.

REWRITTEN PLATFORM

Rewriting Core and Infra logic inside the CLI would create drift, duplication, and fragile maintenance.

Productive K3S CLI is the middle path: one UX layer, explicit bundle resolution, and delegation into the real product contracts.

Keep Core and Infra authoritative
Make published releases first-class
Give users one ergonomic entrypoint

Typical usage

  • Run remote Multipass and on-prem scenarios from a workstation
  • Validate profiles before provisioning
  • Inspect the exact Core or Infra bundle selected for execution
  • Use the same CLI locally in development and remotely through published releases

Design principles

  • Delegate, do not duplicate: the CLI should route into Core and Infra, not absorb their implementation
  • Remote first: published bundles are the default user path and must be validated as products
  • Explicit local mode: development workflows can still target sibling repositories when requested

Where it fits

  • User laptops and operator workstations
  • CI pipelines validating published Productive K3S bundles
  • Development setups consuming local sibling repositories explicitly
  • Cross-platform CLI distribution for Linux, macOS, and Windows

What it is not

  • Not a replacement for Productive K3S Core
  • Not a replacement for Productive K3S Infra
  • Not an excuse to hide version resolution or bundle provenance

It is the UX and release-aware orchestration layer above Core and Infra.