{
  "id": 17067718,
  "title": "Why Kubernetes platforms keep rebuilding a layer they could share",
  "url": "https://urgent.news/2026/10/29/why-kubernetes-platforms-keep-rebuilding-a-layer-they-could-share",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-29T13:00:00.000Z",
  "source": {
    "name": "The New Stack",
    "slug": "the-new-stack",
    "url": "https://thenewstack.io/kubernetes-resource-composition-layer/"
  },
  "original_language": "en",
  "account": "Kubernetes platform teams frequently develop controllers that create a series of objects and copy fields between them, often without any underlying recipe. These controllers include a Deployment, a Service in front of it, and a ConfigMap with a hostname field. While they utilize Kubernetes components like CRDs, Controllers, Server-side Apply, CEL, and OpenAPI schemas, they construct their own solutions for resource dependencies and ordering, often leading to duplicated effort across organizations. The Kube Resource Orchestrator (kro) seeks to address this by providing a shared primitive that can be built upon by other tools, rather than creating another end-to-end platform. Kro breaks down the controller into two components: a composition (template with resources and CEL expressions) and an API (schema, CRD, and instances). By deriving a dependency graph from the CEL expressions and type-checking the expressions against the OpenAPI schema, kro ensures that the order of resources is derived rather than explicitly declared, preventing drift caused by manual ordering. This approach allows application teams to interact with the platform using standard Kubernetes APIs, and kro enforces that changes to the schema do not break existing instances. Additionally, kro offers a Graph primitive for cases where a set of existing resources need to be composed and automatically updated based on changes to the cluster. This abstraction reduces the need for multiple custom APIs and simplifies the management of resource dependencies in Kubernetes environments.",
  "summary": "Ask a platform team what they built last year, and the list likely includes a Kubernetes controller that creates a The post Why Kubernetes platforms keep rebuilding a layer they could share appeared first on The New Stack .",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}