Why this repository exists
PRODUCT REPOS
Core, infra, CLI, addons, and pro profiles each own their implementation details and release logic.
PUBLIC UMBRELLA
Users still need one place to understand the ecosystem, choose a path, and navigate the repositories coherently.
Productive K3S provides that shared public entry point.
Explain how the repositories fit together
Point users to the right starting workflow
Keep ecosystem positioning and roadmap in one place
What you can do from here
- Understand the split between core, infra, cli, addons, and infra-pro
- Choose a practical starting point for installation or evaluation
- Follow the public direction of the ecosystem
- Reach the repository that owns the implementation you need
Portal principles
- Public by design: this site explains the ecosystem without leaking private operational detail
- Repository-linked: implementation belongs in the owning repository, not duplicated here
- Bilingual entry point: English and Spanish should both remain first-class for public navigation
Main ecosystem repositories
- productive-k3s-core for runtime and base installation
- productive-k3s-infra for assembled infrastructure scenarios
- productive-k3s-cli for the user-facing command line
- productive-k3s-addons for optional extensions and examples
- productive-k3s-infra-pro for private or commercial profiles
What this repository is not
- Not the core installation engine
- Not the place for infrastructure implementation details
- Not a substitute for the owning product repositories
It is the public connective layer across the Productive K3S ecosystem.