🔹 Feature: Forget Terraform, Bicep & ARM — Try Azure Service Operator (ASO)
🔹 What It Does: Azure Service Operator lets you deploy and manage Azure resources directly from your Kubernetes cluster using native K8s tooling — CRDs, kubectl, GitOps. The way it was meant to be. 😄
What Is It Giving You:
✅ True K8s-Native IaC Define Azure resources as Kubernetes Custom Resources — no HCL, no JSON, no YAML-disguised-ARM. Just pure CRD goodness.
✅ Azure Resource Lifecycle via K8s Garbage Collection ASO models Azure resource ownership using native K8s ownership references. Delete the parent, children follow. Clean and predictable.
✅ Cloud Scale — Powered by ARM Schemas CRDs are auto-generated from Azure Resource Manager schemas, so ASO keeps pace with new Azure services. 150+ resources supported and growing every release.
✅ Async Reconciliation ASO never blocks on resource creation. Your cluster stays responsive while Azure does its thing in the background.
✅ GitOps-Ready Pair ASO with Flux or ArgoCD and your entire Azure infrastructure becomes a pull request. That’s the dream. 🚀
💡 Terraform fans — I know. But once you manage an AKS cluster AND its Redis Cache AND PostgreSQL AND Key Vault all from the same kubectl apply, there’s no going back. 😏
