Crossplane Intro & Deep Dive - Compose Your Custom Cloud Platform
summary
Crossplane lets teams compose custom platform APIs declaratively—no controller code required—by wiring XRDs, Compositions and provider CRDs into Kubernetes. Demos use provider-jet-aws, kubectl and controller-runtime to create an S3 bucket, an RDS instance plus parameter group, and a new Elasticache subnet group (providers can expose >700 CRDs); reconciliation is asynchronous and uses an externalName link and patches with runtime transforms. The provider generator builds and runs locally and the resources appear in AWS, proving the approach works.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:30What is Crossplane?
- 2:08CNCF Project for the Community
- 2:37Project and Community Stats
- 5:18Managed Resource Reconciliation
- 11:36Build your own Platform API
- 13:05Composite Resources
- 13:51Compositions
- 14:19Patches
- 22:15Extension Points
- 24:06Crossplane Provider Ecosystem
- 25:12Control Plane Internal Stack
related talks
32mCrossplane: Compose Infrastructure and Services Into...
37mPlatformOps with Crossplane
13mKeynote: Crossplane Is the Answer! but What Is the Question?
11mLightning Talk: Connecting the (platform) pieces for automated CI/CD - Jan Willies, Accenture
35mExpanding Interoperability in the CD Ecosystem
38mCNCF Cross-Cloud CI Deep Dive
30mGitOpsifying Cloud Infra with Crossplane, ArgoCD
01h 29mTutorial: Build Your Own Heroku With Cloud Native Stack