Crossplane

crossplane.io ↗

A Kubernetes-based framework for provisioning infrastructure through composable APIs.

SI Score
75/100
Pricing
Open Source AI reading, not confirmed
Free plan
Not confirmed
Sign-up required
Not confirmed

Ask SI about Crossplane

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the Crossplane homepage

What it does

Crossplane extends the Kubernetes control plane so platform teams can define APIs for applications and infrastructure resources. Providers connect the control plane to external resource types, while compositions group lower-level managed resources behind a higher-level composite resource. Crossplane handles the infrastructure-provisioning and reconciliation stage; it is not a source-code build or test runner.

From infrastructure pieces to a platform API

Crossplane installs into an existing Kubernetes cluster; the official installation guide lists an actively supported Kubernetes version and Helm 3.2 or later as prerequisites. After installation, a platform team connects a provider and defines a composite-resource interface plus a Composition that maps a consumer's request to managed resources. Consumers then work through Kubernetes-style resources rather than hand-assembling every provider object. Crossplane reconciles the declared resource state against the managed resources described by the configuration.

This puts Crossplane in the infrastructure and platform-provisioning part of delivery, before or alongside application rollout. It can standardize how teams request infrastructure, but it does not compile application source or execute unit tests. The composition guide uses Kubernetes tools such as kubectl to work with resources; its examples are documentation, not commands run for this listing.

The upstream project is open source under Apache License 2.0. The collection entry covers the Crossplane framework itself, not a separate vendor-hosted control plane or support plan.

Strengths

  • Compositions let a platform expose a higher-level resource API while orchestrating underlying managed resources.
  • The framework builds on Kubernetes resource and control-plane conventions.

Watch out for

  • Crossplane requires an existing supported Kubernetes cluster and Helm 3.2 or later; external resource types also need provider configuration.
  • Its main role is infrastructure orchestration and reconciliation, so application builds and tests need other tools.

Best for

  • Platform teams creating self-service APIs for repeatable infrastructure provisioning.
  • Organizations standardizing how application teams request cloud resources through Kubernetes-style declarations.

Sources