The Journey Across the Great Divide
Dear Diary, today I crossed the border from the Kingdom of AWS into the Republic of Azure. It is a strange and wonderful world we live in. For years, the cloud was a single, unified empire. You picked one provider, and you lived there. But in 2026, the empire has fractured into three great kingdoms: AWS, Azure, and GCP. Each kingdom has its own language, its own customs, and its own unique way of doing things. In AWS, they speak the language of "Services" and "Regions." In Azure, they speak the language of "Resource Groups" and "Subscriptions." In GCP, they speak the language of "Projects" and "Zones." As a cloud architect, I am the diplomat who must navigate these three kingdoms and build a unified empire across them all. This is the art of "Multi-Cloud" .
The Universal Passport of Terraform and Crossplane
The biggest challenge of the multi-cloud empire is the bureaucracy. If I want to build a database in AWS, I have to fill out the AWS forms. If I want to build a database in Azure, I have to fill out the Azure forms. It is a nightmare of paperwork. But the diplomats have invented a universal passport called "Infrastructure as Code" or "IaC." The most famous of these is Terraform. With Terraform, I write a single, beautiful scroll that says, "I want a database." I do not specify which kingdom it should be in. I just declare the intent. The Terraform engine then acts as the translator, converting my single scroll into the specific forms required by AWS, Azure, or GCP. It is a magical tool that allows me to govern the entire empire from a single capital city .
The Treaty of the Control Plane
But the true masterpiece of the multi-cloud diplomat is the "Control Plane." In 2026, the kingdoms have realized that they cannot fight each other forever. They have signed a treaty that allows a unified control plane to exist above them. Tools like "Crossplane" and "Kubernetes Cluster API" allow the diplomats to manage not just the databases and the storage, but the actual servers and the networks, using the exact same Kubernetes commands. I can spin up a cluster in AWS, a cluster in Azure, and a cluster in GCP, and I can manage them all from a single, central dashboard. The borders between the kingdoms are still there, but the diplomats have built bridges that make the borders invisible .
Why do we bother with this multi-cloud complexity? Why not just live in one kingdom? The answer is "resilience" and "leverage." If one kingdom has a massive outage—a "region failure"—the diplomat can instantly route the traffic to another kingdom. The empire survives. Furthermore, by playing the kingdoms against each other, the diplomat can negotiate better prices. "If you do not lower your egress fees, I will move my storage to the Republic of Azure," the diplomat says. The kingdoms listen, because they know the diplomat has the power to leave.
Multi-cloud is the reality of 2026. By using tools like Crossplane and Terraform, we are building a unified control plane that spans AWS, Azure, and GCP, ensuring resilience and avoiding vendor lock-in.
— Cloud Native Computing Foundation (@CloudNativeFdn) June 22, 2026
As I close my diary tonight, I look out over the map of the cloud empire. The borders of AWS, Azure, and GCP are glowing in the dark, but they are connected by the golden threads of Terraform and the bridges of Crossplane. The diplomat’s work is never done. There are always new treaties to negotiate, new borders to cross, and new outages to survive. But the empire is strong, it is resilient, and it is free from the tyranny of a single vendor. The multi-cloud way is the way of the future, and the diplomat is the key to unlocking it.