The How & Why for Building Crossplane Providers - Krish Chowdhary, Red Hat
summary
Explains how Crossplane providers map one-to-one to external APIs using kubebuilder/controller-runtime and CRD generation, and shows bootstrapping from the provider template to a working provider-in-cluster example. Demonstrates implementing observe/create/update/delete methods, wiring a connector to kubeconfig, and exposing Redis endpoint in secret (port 6379 and optional password). Builds a Redis managed resource, deploys Deployment+Service, and proves it works end-to-end in under an hour, noting missing tests and cluster-scale features.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:52What Are Providers
- 2:38Where Are Providers Located
- 3:26When Does It Make Sense To Create a Provider
- 5:44How How Can We Create a Crossplan Provider
- 6:42Components of the Provider and Cluster
- 8:25Command Directory
- 10:40Observe Method
- 11:47Package Directory
- 14:59Scaffold Out the Controller
related talks
23mIntroduction to Crossplane and Simplifying Cloud Native Infrastructure Management
30mBuild Your Own Cluster API Provider the Easy Way
01h 39mWriting Crossplane Providers with Code Generation
01h 19mTutorial: Building an Enterprise Infrastructure Control Plane on Kubernetes
25mCrossplane: Build and Manage Infrastructure using Kubernetes
17mCrossplane: Deploy Your Cloud Components from Your K8S Cluster
31mThe Crossplane Experience
35mBuilding and Enabling APIs with Crossplane 1