-
Notifications
You must be signed in to change notification settings - Fork 0
CNOE
CNOE (Cloud Native Operational Excellence) is an open community initiative for building Internal Developer Platforms (IDPs) using curated CNCF open-source projects. Led by companies running IDPs at scale — including AWS, Adobe, Salesforce, Intuit, and Cisco — it provides opinionated reference architectures, integration guidance, and shared tooling rather than a single installable product. The project is hosted at github.com/cnoe-io.
The reference stack combines established CNCF projects: ArgoCD (GitOps continuous delivery), Crossplane (infrastructure provisioning via Kubernetes CRDs), Backstage (developer portal and service catalogue), Keycloak (identity and access management), and Argo Workflows (workflow orchestration). CNOE's contribution is the wiring and opinionated guidance for how these components integrate at scale.
Placed in Platforms / Assess / outer.
CNOE addresses a real problem: organisations building IDPs independently converge on similar tool combinations but reinvent the integration layer each time. The initiative codifies the patterns from companies already operating at scale, reducing the research and trial-and-error cost of IDP construction.
Outer position reflects three constraints. First, scope: CNOE is relevant only to teams operating Kubernetes at meaningful scale with a dedicated platform engineering function — it is out of scope for solo practitioners or small teams without IDP requirements. Second, constituent complexity: the reference stack (ArgoCD + Crossplane + Backstage + Keycloak + Argo Workflows) carries significant individual adoption cost before the integration layer delivers value. Third, maturity as guidance: CNOE is primarily reference architecture and community consensus rather than a deployable product with a clear quickstart path.
Worth tracking for any team beginning a platform engineering initiative at Kubernetes scale. The constituent tools (ArgoCD, Crossplane, Backstage) are individually worth assessing before evaluating the combined CNOE reference architecture.
Trial gate: at least two constituent CNOE tools deployed and integrated in a real platform engineering context, with the CNOE reference architecture consulted as a design input.