I set up Crossplane to provision and manage cloud resources from Kubernetes — letting your development teams self-serve databases, buckets, queues, and networking through the same kubectl and GitOps workflows they already use for application deployments.
Setup includes: Crossplane core installed on your cluster; cloud provider configuration (AWS, GCP, or Azure) with least-privilege credentials; Managed Resources for your target infrastructure (RDS, S3, Cloud SQL, GCS, Azure SQL, etc.); Compositions and CompositeResourceDefinitions (XRDs) that expose simplified abstractions to developer teams; RBAC so teams can request infrastructure without cluster-admin rights; and GitOps integration via ArgoCD or Flux.
The XRDs I write become your platform API — a developer fills in a few fields (environment, size, region) and Crossplane provisions the exact infrastructure configuration your platform team has approved, every time.
This is platform engineering work. Best suited for teams building internal platforms where developer self-service and infrastructure consistency are priorities.