Daniel, I get your point, but that is not what I meant with drift detection. In Kubernetes you have automatic drift detection because Kubernetes will constantly check if your resource' current state matches its desired state. If drift is deteted, Kubernetes will reconcile the state and attempt to match the desire state. Since Crossplane is running as CRDs in Kubernetes and using its APIs, Crossplane will have automatic drift detection too. In Terraform it will always be a manual or scheduled "terraform plan" needed to detect and reconcile drift.
Sign up to discover human stories that deepen your understanding of the world.
Free
Distraction-free reading. No ads.
Organize your knowledge with lists and highlights.
Tell your story. Find your audience.
Membership
Read member-only stories
Support writers you read most
Earn money for your writing
Listen to audio narrations
Read offline with the Medium app
Written by Audun Nes
Lead Cloud Engineer/Site Reliability Engineer from Copenhagen, Denmark. GitHub: https://github.com/avnes
Fundamentally different approaches to Orchestration here…Terraform uses a closed, proprietary config language in HCL (lol - literally named after the company). I’ve been working with some of HC’s largest customers (FSI) and they’re reducing their…
--
