Doing GitOps for multi-cloud using Crossplane & Flux2
summary
Bootstraps a cluster with Flux2 bootstraps repo and cluster then uses Flux2 helm CRDs to install Crossplane provisions Cloud SQL and RDS from manifests; configures AWS and GCP provider packages and providerConfigs with secrets, pushes manifests to a GitHub repo, and sees a Cloud SQL instance on GCP and an RDS instance on AWS created and later destroyed when manifests are removed. Connection details appear as connection secrets written into Kubernetes, and reconciliation runs automatically.
AI-written summary · about
chapters (14)
- 0:00GitOps and multi-cloud intro
- 1:43GitOps four principles
- 4:27Crossplane for multi-cloud
- 5:30Flux for Kubernetes
- 6:12Live demo setup
- 7:41Bootstrapping cluster
- 11:12Installing Crossplane
- 13:18Multi-cluster repo structure
- 15:11Crossplane providers setup
- 18:43Deploying cloud resources
- 26:55Provisioning RDS and Cloud SQL instances
- 30:25Accessing DB secrets
- 31:50Cleaning up resources
- 32:32Summary and future
related talks
48mDoing multi-provider Kubernetes in GitOps mode with CrossPlane
31mCrossplane + Flux2
39mEnhance Your Kubernetes Experience with GitOps & Flux
27mGitOps Based Infrastructure as Code with Rancher Fleet and Crossplane
49mGitOps, a somewhat realistic scenario on Kubernetes with Flux
37mPlatformOps with Crossplane
01h 01mManaging Kubernetes the GitOps way with Flux
24mHosting Applications in the Real World
