OneK8s
One Kubernetes platform, one application contract for every cloud – built on Azure (AKS) first. What the platform must do is in the requirements; how it does it is the design.
Status: draft for review (release notes). Country codes
fi/seand all IP ranges are examples.
How we work: requirements-driven collaboration
Part 0 is the human side: requirements and
acceptance criteria. Parts 1 to 8 are the AI’s design, checked against
them. CODEOWNERS and the required check Approvals enforce who approves what: the author counts as their own
side’s approval, and an approval is kept across later pushes that do not touch that owner’s files.
Where to start
| You are | Read |
|---|---|
| Someone who sets or changes a requirement | 0.2 Requirements and 0.3 Acceptance criteria |
| A reviewer or sponsor | 1.0 Summary, then 1.2 for how the design meets each requirement |
| The security team | Part 2 Inside a cluster, 4 Encryption and 5 Egress control, then 2.4’s isolation matrix |
| An application team | 1.4 The application contract |
| An operator | Part 3 The fleet and 6 Operations |