Why this repository exists

REAL KUBERNETES

Teams want real Kubernetes capabilities without starting from a painful operational jump.

↔ ↕

CLEAR PATH

Users still need one place to understand the model, start simply, and move across the ecosystem without losing continuity.

Productive K3S is the public path that connects those pieces into one product story.

Explain the conceptual model before the technical detail

Show how the pieces fit without forcing one single interface

Guide users toward the right starting path

Component map

• Core: start with a real Kubernetes base in the simplest practical way
• Infra: deploy complete solutions on different platforms
• Profiles: use curated solutions ready to deploy
• Addons: extend the cluster with curated packages
• CLI: use the simplest and recommended unified interface

Portal principles

• Solution-first: start with what the ecosystem enables before diving into how the internals are split
• Repository-linked: technical depth belongs in the owning repository, not duplicated here
• Bilingual path: English and Spanish remain first-class for the public path into the ecosystem

Recommended ways to start

• I want to start simple: begin with Productive K3S Core
• I want to deploy a complete solution: continue to Infra and Profiles
• I want one recommended interface for the whole experience: use Productive K3S CLI
• I want to understand how the pieces fit: open the ecosystem model pages

What this repository is not

• Not the place for deep implementation detail of every component
• Not the only way to enter the ecosystem
• Not a substitute for the owning product repositories

It is the public product path across the Productive K3S ecosystem.