Why it exists
START SIMPLE
Teams want a first step into Kubernetes that feels useful immediately instead of turning into a platform project on day one.
REAL CONTRACTS
A simpler starting point should still preserve real Kubernetes workflows and leave room for more demanding scenarios later.
Productive K3S Core is that practical first step.
Start with a usable Kubernetes base
Keep the operational model simple
Grow later without replacing the foundations
Target use cases
- Teams starting their Kubernetes journey
- Small platforms that need a useful base quickly
- Development and evaluation environments
- Deployments that may later grow into more demanding scenarios
Design principles
- Start with the useful path: install a base you can actually use, not a demo shell
- Stay Kubernetes-native: keep the real Kubernetes operating model visible
- Keep room to grow: support more demanding scenarios and advanced engines without changing the core contract
How to use Core
- Use Core directly when you want the clearest path to the base Kubernetes installation contract
- Use Core directly when you want explicit control over cluster base setup and addon or stack installation
- Use Productive K3S CLI when you want the simplest and recommended ecosystem experience
- Advanced users can extend the model beyond k3s, including rke2 and alternate engine contracts such as k3sup
What it is not
- Not a full platform that hides Kubernetes from you
- Not a promise that every deployment should remain forever in the simplest topology
- Not a reason to skip operational discipline
Instead, it is the simple first step into the wider Productive K3S path.