Crossplane — The Cloud Native Control Plane Framework

What it is

Crossplane is an open-source framework that extends Kubernetes with Custom Resource Definitions (CRDs) representing cloud infrastructure. Instead of using separate tools like Terraform or CloudFormation, you define AWS, Azure, GCP, and SaaS resources as Kubernetes objects and manage them with kubectl and GitOps workflows.

Crossplane targets platform engineers building internal developer platforms. It lets teams offer self-service infrastructure provisioning through Kubernetes APIs without exposing raw cloud provider consoles.

How it saves time or tokens

Crossplane unifies infrastructure management into the Kubernetes API you already know. No separate CLI, no separate state files, no separate CI pipeline for infrastructure. Changes flow through the same GitOps pipeline as application code. For AI-assisted workflows, agents that understand Kubernetes YAML can manage infrastructure without learning provider-specific tools.

How to use

1. Install Crossplane into your Kubernetes cluster.
2. Install a provider (e.g., provider-aws, provider-gcp).
3. Configure provider credentials.
4. Create infrastructure by applying Kubernetes manifests.

# Install Crossplane via Helm
helm repo add crossplane-stable https://charts.crossplane.io/stable
helm install crossplane crossplane-stable/crossplane \
  --namespace crossplane-system --create-namespace

# Install AWS provider
cat <<EOF | kubectl apply -f -
apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-aws-s3
spec:
  package: xpkg.upbound.io/upbound/provider-aws-s3:v1.1.0
EOF

Example

Creating an S3 bucket with Crossplane:

apiVersion: s3.aws.upbound.io/v1beta1
kind: Bucket
metadata:
  name: my-crossplane-bucket
spec:
  forProvider:
    region: us-east-1
    tags:
      Environment: production
      ManagedBy: crossplane
  providerConfigRef:
    name: aws-provider-config

Apply it like any Kubernetes resource:

kubectl apply -f bucket.yaml
kubectl get bucket my-crossplane-bucket

Related on TokRepo

• DevOps tools — Infrastructure and deployment tools
• Automation tools — Workflow and infrastructure automation

Common pitfalls

• Crossplane requires a running Kubernetes cluster. It adds operational complexity on top of cluster management.
• Provider coverage varies. Not every AWS/GCP/Azure resource has a Crossplane equivalent. Check provider documentation before committing.
• Debugging failed resource provisioning requires reading Crossplane events and provider logs, which differs from standard kubectl troubleshooting.
• Composition resources (XRDs) have a learning curve. Start with managed resources before building abstractions.
• State drift detection works differently from Terraform. Crossplane continuously reconciles, which can override manual changes in the cloud console.
• Review the official documentation before deploying to production to ensure compatibility with your specific environment and requirements.
• Start with default settings and customize incrementally. Changing too many configuration options at once makes debugging harder.
• Keep your installation updated to the latest stable version. Security patches and bug fixes are released regularly.