Installation¶
What gets installed¶
The installer places the pk3s executable in your PATH.
It does not install Productive K3S Core or Productive K3S Infra bundles up front. Those are resolved on demand when you run a command.
Unix-like install¶
Install from the public script:
By default the installer writes to:
After installation:
Windows¶
The CLI executable is intended to be published as a native Windows binary too.
For this first release, the recommended user-facing flow is:
- Download the Windows release asset.
- Put
pk3s.exein a directory that is already inPATH, or add its directory toPATH. - Run:
Local source install¶
If you are working from the repository itself:
Bundle cache¶
The CLI stores downloaded bundles in a local cache.
Typical paths:
- Linux/macOS:
~/.cache/pk3s - Windows:
%LocalAppData%\pk3s