Okay, I know this is a Kubernetes tooling forum, but I have to ask because I'm coming at this from a design systems and infrastructure-as-code angle. I've been deep in Figma trying to prototype a unified dashboard for our dev and design teams, and the resource sprawl across AWS, Vercel, and a few SaaS tools is becoming a real headache for user workflows.
We use ArgoCD for our Kubernetes manifests, and it's fantastic for that. But I keep hearing about Crossplane being able to manage *anything* as a Kubernetes custom resource. The promise of using a single GitOps flow for our Postgres databases, CloudFront distributions, and even things like Auth0 tenants or SendGrid configurations sounds almost too good to be true.
Has anyone here actually tried using Crossplane in a GitOps setup for primarily non-K8s resources? I'm curious about the day-to-day reality. How's the feedback loop? When you push a manifest change for, say, an S3 bucket, is it as smooth as updating a Deployment? And what about the learning curve for developers who aren't steeped in Kubernetes concepts? I worry about the cognitive load for our team.
I'd love to hear about real configs and where you might have hit snags, especially around monitoring and debugging when something goes wrong. Does it feel like a coherent experience, or more like patching together different worlds?