Tool Review: The Shift from GitOps to 'Control-Plane-Ops' via Crossplane
GitOps—using Git as the single source of truth for declarative infrastructure—revolutionized how we manage Kubernetes. But in 2026, for large-scale, multi-cloud platform engineering teams, GitOps is hitting a ceiling.
The friction point? GitOps tools (like ArgoCD) are excellent at reconciling state within a cluster, but they struggle with abstracting the complexities of the underlying cloud infrastructure across clusters.
Enter Crossplane, the CNCF incubating project that is rapidly becoming the standard for modern infrastructure management. Crossplane shifts the paradigm from GitOps to Control-Plane-Ops.
Why It Matters: From Configuration Files to API Abstractions
GitOps relies on constantly applying myriad YAML manifests. It’s file-based management. Crossplane, however, turns your Kubernetes cluster into a universal control plane. It allows you to define cloud infrastructure (AWS RDS, GCP GKE, Azure CosmosDB) using Kubernetes Custom Resource Definitions (CRDs).
Instead of a developer pushing a YAML file to Git which then triggers an apply, the developer makes an API call to the Kubernetes control plane, which then reconciles the actual cloud infrastructure.
Teaching Point: How Crossplane Differs from Terraform
Terraform (Imperative/Run-Based): You run terraform apply. It creates infrastructure, then stops. It requires an external state file. Drift detection requires a scheduled re-run. Excellent for initial provisioning.
Crossplane (Declarative/Continuous Reconciliation): It runs inside Kubernetes. It constantly monitors the desired state of your infrastructure against the actual state in the cloud provider, just like a Kubernetes Deployment controller manages pods. If an AWS S3 bucket is manually deleted, Crossplane immediately detects the drift and re-provisions it based on the CRD definition.
Crossplane unifies application and infrastructure state into a single, constantly reconciling loop.
Discussion Question
For platform engineers managing hybrid environments: Are you actively looking to replace your Terraform pipelines with a pure Kubernetes Control-Plane approach using Crossplane, or do you see them coexisting? What has been the biggest hurdle in adopting Crossplane's CRD model?
CTA (Join Cloud, DevOps & Open Source)
Ready to master advanced Kubernetes patterns, platform engineering, and the next generation of IaC? Join Cloud, DevOps & Open Source to connect with fellow engineers architecting the future of scalable infrastructure.
GitOps—using Git as the single source of truth for declarative infrastructure—revolutionized how we manage Kubernetes. But in 2026, for large-scale, multi-cloud platform engineering teams, GitOps is hitting a ceiling.
The friction point? GitOps tools (like ArgoCD) are excellent at reconciling state within a cluster, but they struggle with abstracting the complexities of the underlying cloud infrastructure across clusters.
Enter Crossplane, the CNCF incubating project that is rapidly becoming the standard for modern infrastructure management. Crossplane shifts the paradigm from GitOps to Control-Plane-Ops.
Why It Matters: From Configuration Files to API Abstractions
GitOps relies on constantly applying myriad YAML manifests. It’s file-based management. Crossplane, however, turns your Kubernetes cluster into a universal control plane. It allows you to define cloud infrastructure (AWS RDS, GCP GKE, Azure CosmosDB) using Kubernetes Custom Resource Definitions (CRDs).
Instead of a developer pushing a YAML file to Git which then triggers an apply, the developer makes an API call to the Kubernetes control plane, which then reconciles the actual cloud infrastructure.
Teaching Point: How Crossplane Differs from Terraform
Terraform (Imperative/Run-Based): You run terraform apply. It creates infrastructure, then stops. It requires an external state file. Drift detection requires a scheduled re-run. Excellent for initial provisioning.
Crossplane (Declarative/Continuous Reconciliation): It runs inside Kubernetes. It constantly monitors the desired state of your infrastructure against the actual state in the cloud provider, just like a Kubernetes Deployment controller manages pods. If an AWS S3 bucket is manually deleted, Crossplane immediately detects the drift and re-provisions it based on the CRD definition.
Crossplane unifies application and infrastructure state into a single, constantly reconciling loop.
Discussion Question
For platform engineers managing hybrid environments: Are you actively looking to replace your Terraform pipelines with a pure Kubernetes Control-Plane approach using Crossplane, or do you see them coexisting? What has been the biggest hurdle in adopting Crossplane's CRD model?
CTA (Join Cloud, DevOps & Open Source)
Ready to master advanced Kubernetes patterns, platform engineering, and the next generation of IaC? Join Cloud, DevOps & Open Source to connect with fellow engineers architecting the future of scalable infrastructure.
Tool Review: The Shift from GitOps to 'Control-Plane-Ops' via Crossplane
GitOps—using Git as the single source of truth for declarative infrastructure—revolutionized how we manage Kubernetes. But in 2026, for large-scale, multi-cloud platform engineering teams, GitOps is hitting a ceiling.
The friction point? GitOps tools (like ArgoCD) are excellent at reconciling state within a cluster, but they struggle with abstracting the complexities of the underlying cloud infrastructure across clusters.
Enter Crossplane, the CNCF incubating project that is rapidly becoming the standard for modern infrastructure management. Crossplane shifts the paradigm from GitOps to Control-Plane-Ops.
Why It Matters: From Configuration Files to API Abstractions
GitOps relies on constantly applying myriad YAML manifests. It’s file-based management. Crossplane, however, turns your Kubernetes cluster into a universal control plane. It allows you to define cloud infrastructure (AWS RDS, GCP GKE, Azure CosmosDB) using Kubernetes Custom Resource Definitions (CRDs).
Instead of a developer pushing a YAML file to Git which then triggers an apply, the developer makes an API call to the Kubernetes control plane, which then reconciles the actual cloud infrastructure.
Teaching Point: How Crossplane Differs from Terraform
Terraform (Imperative/Run-Based): You run terraform apply. It creates infrastructure, then stops. It requires an external state file. Drift detection requires a scheduled re-run. Excellent for initial provisioning.
Crossplane (Declarative/Continuous Reconciliation): It runs inside Kubernetes. It constantly monitors the desired state of your infrastructure against the actual state in the cloud provider, just like a Kubernetes Deployment controller manages pods. If an AWS S3 bucket is manually deleted, Crossplane immediately detects the drift and re-provisions it based on the CRD definition.
Crossplane unifies application and infrastructure state into a single, constantly reconciling loop.
Discussion Question
For platform engineers managing hybrid environments: Are you actively looking to replace your Terraform pipelines with a pure Kubernetes Control-Plane approach using Crossplane, or do you see them coexisting? What has been the biggest hurdle in adopting Crossplane's CRD model?
CTA (Join Cloud, DevOps & Open Source)
Ready to master advanced Kubernetes patterns, platform engineering, and the next generation of IaC? Join Cloud, DevOps & Open Source to connect with fellow engineers architecting the future of scalable infrastructure.
Arabic
French
Spanish
Portuguese
Deutsch
Turkish
Dutch
Italiano
Russian
Romaian
Portuguese (Brazil)
Greek