The New Stack: Why Kubernetes platforms keep rebuilding a layer they could share
The article argues that many Kubernetes tools rebuild the same composition layer for grouping resources, ordering them, and passing values between them. It describes kro's ResourceGraphDefinition, which expresses dependencies as CEL references that set order, and kro 0.10's Graph primitive, which runs composition without a custom API. The author suggests composition could be a shared primitive in Kubernetes.
What changes for platform teams
Platform teams that write glue controllers or ordering logic between Helm, Argo CD or Crossplane resources can consider expressing dependencies as references in one shared composition layer. Teams adopting it would take on ownership of every API they publish, since schema changes can break existing instances.
Read the original at The New Stack ↗
written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules