Crossplane: Kubernetes-driven Infrastructure-as-Code for Platform Teams
Blent.ai has published an insightful article today, June 17, 2026, exploring the transformative capabilities of Crossplane in the realm of cloud infrastructure management. The piece, titled "Crossplane : infrastructure-as-code piloté depuis Kubernetes," positions Crossplane as a pivotal tool for organizations embracing Kubernetes as their central platform. It addresses the common challenge faced by platform engineering teams: how to manage diverse cloud infrastructure components, such as databases, storage buckets, and networks, with the same declarative approach used for applications.
The article explains that Crossplane effectively extends Kubernetes, turning the cluster into a universal control plane capable of provisioning and managing resources across any cloud provider. This approach allows development teams to provision their required resources without relying on a multitude of disparate tools and processes. A core tenet highlighted is Crossplane's continuous reconciliation model, which is characteristic of Kubernetes controllers. Once an infrastructure resource is declared, Crossplane constantly monitors its state and automatically corrects any deviations, ensuring that the actual state consistently matches the desired declared state. This mechanism helps to eliminate issues like state lock and desynchronized states often encountered in traditional IaC tools.
One of the most significant features discussed is Crossplane's Compositions. These enable platform teams to define high-level abstractions that encapsulate the underlying complexity of infrastructure. For instance, a platform team can create a "PostgreSQLDatabase" abstraction. When a developer requests this, Crossplane automatically provisions a managed RDS instance, configures appropriate security groups, creates DNS entries, and generates Kubernetes secrets containing credentials. This simplified interface, exposed to development teams via a 'Claim', greatly enhances developer experience and operational efficiency.
The article also draws a comparison between Crossplane and Terraform, acknowledging that both address the fundamental need for declarative infrastructure management. However, it points out key differences: Terraform operates on a punctual execution model where `terraform apply` calculates and applies changes, storing state in a file. Crossplane, conversely, leverages Kubernetes' continuous reconciliation, storing state in etcd and benefiting from the cluster's native high availability. The benefits of Crossplane's approach are summarized as tool unification (a single interface like `kubectl`, a single language like YAML, and a unified workflow for applications and infrastructure), continuous reconciliation for drift detection and correction, and native GitOps integration, allowing tools like ArgoCD or Flux to manage infrastructure alongside applications without specific configurations.
Read original source