Skip to main content
South Korea
AIMenta
C

Crossplane

by CNCF

Open-source CNCF Kubernetes add-on that extends the Kubernetes control plane to manage cloud infrastructure (AWS, GCP, Azure, Alibaba Cloud) as Kubernetes custom resources, enabling APAC platform teams to compose and provision infrastructure through GitOps workflows.

Visit Crossplane (opens in new tab) Get a recommendation
AIMenta verdict
Recommended
5/5

"Crossplane is the open-source Kubernetes control plane extension for APAC platform engineering — cloud infrastructure as Kubernetes custom resources. Best for APAC platform teams wanting to provision AWS, GCP, and Azure resources from Kubernetes with GitOps-native workflows."

Features
7
Use cases
4
Watch outs
4
What it does

Key features

  • Provider model — AWS, GCP, Azure, Alibaba Cloud, and community providers extending Kubernetes API with cloud CRDs
  • Managed resources — Kubernetes CRDs mapping 1-to-1 with APAC cloud resources (RDS, GCS bucket, AKS cluster)
  • Composite resources — compose multiple cloud resources into opinionated application-scoped abstractions for APAC developer platforms
  • Claims — developer-facing interface for requesting composed infrastructure without cloud-specific knowledge
  • GitOps native — all Crossplane resources are Kubernetes objects reconcilable via Flux or ArgoCD for APAC GitOps
  • RBAC integration — Kubernetes RBAC controls who can create which Crossplane resources in APAC clusters
  • Terraform provider — bridge existing Terraform modules into the Crossplane Kubernetes reconciliation model
When to reach for it

Best for

  • APAC platform engineering teams building internal developer platforms where developers self-service infrastructure through Kubernetes Claims
  • Engineering organisations wanting infrastructure-as-code managed through the same GitOps workflow as APAC Kubernetes application manifests
  • APAC platform teams replacing Terraform with a Kubernetes-native continuous reconciliation model for cloud resource management
  • Engineering teams managing multi-cloud APAC infrastructure across AWS, GCP, and Azure from a unified Kubernetes control plane
Don't get burned

Limitations to know

  • ! Crossplane learning curve is steep — provider CRDs, XRDs, Compositions, and Claims are powerful but require significant investment to understand for APAC platform teams new to Kubernetes control plane extension
  • ! Crossplane is not a Terraform replacement for all use cases — APAC teams with complex Terraform module ecosystems should evaluate migration cost; Crossplane Terraform provider bridges this gap partially
  • ! Crossplane Composition debugging is complex — composition errors manifest as APAC Kubernetes events that require understanding the full Managed Resource and Composite Resource reconciliation model to diagnose
  • ! Crossplane provider maturity varies — AWS and GCP providers are mature; some APAC-specific cloud provider resources may have limited Crossplane provider coverage
Context

About Crossplane

Crossplane is an open-source CNCF project that extends the Kubernetes control plane to provision and manage cloud infrastructure — AWS RDS databases, GCP Cloud SQL instances, Azure AKS clusters, Alibaba Cloud resources, and any provider with a Crossplane provider — as Kubernetes Custom Resources, enabling APAC platform engineering teams to manage application infrastructure through the same GitOps workflows they use for Kubernetes application manifests.

Crossplane's provider model — where Crossplane providers (AWS, GCP, Azure, Alibaba Cloud, and community providers for Terraform, Helm, and SQL) are installed as Kubernetes deployments that extend the Kubernetes API with cloud-specific CRDs — enables APAC platform teams to create cloud resources by declaring Kubernetes manifest files. An APAC RDS database instance is a Kubernetes `RDSInstance` manifest in Git; Crossplane's AWS provider reconciles the manifest against the AWS API, creating and managing the actual RDS instance.

Crossplane's Composite Resources — where platform teams define high-level `CompositeResourceDefinitions` (XRDs) that compose multiple cloud resources into a single application-scoped abstraction, and developers request instances of these compositions through `Claim` resources — enables APAC platform engineering teams to build internal developer platforms where developers request infrastructure through simple, opinionated interfaces without needing to understand the underlying AWS/GCP/Azure resource configuration.

An APAC internal developer platform built on Crossplane might expose a `PostgreSQLDatabase` Claim that developers request with only a `size` parameter (small/medium/large); Crossplane's Composition translates this Claim into an AWS RDS instance, a Secrets Manager secret, a security group, a subnet group, and a Route53 DNS record — all provisioned automatically, consistently, and auditable through Git history.

Crossplane's GitOps integration — where all Crossplane Managed Resources, Composite Resources, and Claims are Kubernetes objects stored in Git and reconciled by Crossplane's Kubernetes controllers — enables APAC platform teams to apply infrastructure changes through the same Flux or ArgoCD GitOps pipeline used for application deployments, with full Git audit history for APAC infrastructure changes.

Beyond this tool

Where this category meets practice depth.

A tool only matters in context. Browse the service pillars that operationalise it, the industries where it ships, and the Asian markets where AIMenta runs adoption programs.

Or browse All tools · Encyclopedia · Case studies · Rankings