Building a vendor-agnostic IAM platform using crossplane — Stefan Möhrle
summary
Centralized GitOps IAM uses Crossplane + ArgoCD to control Keycloak, Grafana and cloud accounts, converting existing Terraform providers into Crossplane providers so many services are manageable; manifests are generated from YAML value files via two-stage Helm templating and emitted as custom resources; unit tests, schema validation and end-to-end checks prevent accidental revokes; a prototype web app shows merge-request diffs and can write back to the repo; migration stays silent per user and the demo mostly works despite a password hiccup.
AI-written summary · about
chapters (15)
- 0:00Introduction to IAM challenges
- 2:28Speaker introduction and context
- 3:32Starting point and existing system
- 5:00Solution goals and Crossplane intro
- 7:04Web app for permission management
- 8:07Terraform vs Crossplane comparison
- 9:13Transition plan to new architecture
- 11:02Crossplane providers and CRDs
- 13:28Helm templating for flexibility
- 17:19Global variables and testability
- 20:10Live demo setup
- 22:35Demo: Permission changes
- 25:06Demo: Argo CD sync
- 26:28Conclusion and demo wrap-up
- 26:50Q&A session
related talks
27mGitOpsify Everything: When Crossplane Meets Argo CD
37mPlatformOps with Crossplane
31mLearnings From Providing A Platform API With Kubernetes And Crossplane
34mDoing GitOps for multi-cloud using Crossplane & Flux2
48mDoing multi-provider Kubernetes in GitOps mode with CrossPlane
48mBuilding a Cloud Native IaC Platform for an Enterprise by Lev...
17mCrossplane: Deploy Your Cloud Components from Your K8S Cluster
30mGetting to Know Crossplane