Skip to content
Back to Stack Recommender

Crossplane

Crossplane — infrastructure control plane built on Kubernetes.

DevOpsComplex

Stack Components

PlatformCrossplane 1.x
RuntimeKubernetes

Why

Provision cloud resources via K8s CRDs, GitOps for infrastructure as code. Docker is used by 59% of professional developers per the Stack Overflow 2024 survey, and Terraform is used by 65% of organizations for IaC (HashiCorp 2024).

GitOps (ArgoCD, Flux) reduces deployment drift to near-zero by making git the single source of truth.

When

Use for unified app+infra on K8s. Avoid for teams not using K8s.

How

1. Install Crossplane on K8s 2. Configure provider (AWS/Azure/GCP) 3. Define Compositions and XRCs 4. Apply claims

Example

apiVersion: example.org/v1 kind: XDatabase metadata: { name: my-db } spec: parameters: { size: small, region: us-east-1 }

Common Problems

  • ⚠Provider not ready — check provider pod logs
  • ⚠Resource stuck — check managed resource status conditions
  • ⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

  • ✓Use Compositions for reusable infrastructure patterns
  • ✓Enable GitOps with Flux/ArgoCD for Crossplane resources
  • ✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is Crossplane and what projects is it for?

Crossplane — infrastructure control plane built on Kubernetes. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.

How do I spin up a working demo with Crossplane in 10 minutes?

Two steps: (1) Install Crossplane on K8s; (2) Configure provider (AWS/Azure/GCP). Get the local dev server running, then wire one real data source to verify the end-to-end loop.

What is the most common pitfall with Crossplane and how do I avoid it?

The most common pitfall is: Provider not ready — check provider pod logs. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.

What are the best practices for Crossplane?

Best practices for Crossplane include: Use Compositions for reusable infrastructure patterns; Enable GitOps with Flux/ArgoCD for Crossplane resources; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use Compositions for reusable infrastructure patterns" — should be set up at project init to avoid costly rework later.

When should I NOT choose Crossplane?

Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). Crossplane shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.