Azure Service Operator
Azure Service Operator is a free, open-source, self-hosted Kubernetes operator for deploying and maintaining Azure resources with Kubernetes tooling.
What Azure Service Operator is
Azure Service Operator is a free, open-source, self-hosted Kubernetes operator for deploying and maintaining Azure resources with Kubernetes tooling. Users describe Azure resources through Custom Resource Definitions and Go API structures, then the controller compares each desired state with the actual Azure resource. It creates, updates, or deletes resources to reconcile differences, and can provision services such as Redis Cache or PostgreSQL for Kubernetes applications. ASO v2 supports more than 150 Azure resources, with more added in each release, and models ownership through Kubernetes garbage collection. The project describes v2 as stable under the Kubernetes definition of stable. Installation is available through Helm or a GitHub release and requires Kubernetes 1.32 or later plus an Azure subscription. Argo CD or Flux can review changes before application. Deleting an ASO resource also deletes its Azure counterpart unless the documented skip-reconcile annotation is applied first.
Good
- Supports more than 150 Azure resources
- Desired-state reconciliation and drift detection
- Kubernetes ownership and garbage collection
- Helm or GitHub installation
- Argo CD and Flux review workflows
Watch out
- Requires Kubernetes 1.32 or later
- Requires an Azure subscription
- Deleting resources can delete Azure counterparts
- RoleAssignment CRD can enable privilege escalation
Who it suits
It suits Kubernetes users who want to manage Azure resources with kubectl-style tooling and declarative resources. It is intended for teams comfortable operating a self-hosted controller and Azure identities.
Verdict
Azure Service Operator connects Kubernetes resource definitions with Azure lifecycle management and reconciliation. Its broad resource coverage and GitOps integrations are useful, but installation prerequisites and deletion behavior require careful administration.
The facts
Each one read from Azure Service Operator's own pages, with the date it was checked.
Where it runs
- Application configuration
- It can manage Azure resources alongside a Kubernetes application and configure the application to use them, such as a Redis cache or PostgreSQL server.checked 11 Oct 2026
What it does
- Authentication
- ASO authenticates with Azure using an identity or service principal, and the project recommends Azure Workload Identity for production use.checked 11 Oct 2026
- Azure lifecycle
- ASO models Azure resource lifecycle using Kubernetes garbage collection through ownership references.checked 11 Oct 2026
- Deletion behavior
- Deleting an ASO resource from the cluster also deletes its corresponding Azure resource unless the documented skip-reconcile annotation is applied first.checked 11 Oct 2026
- GitOps integrations
- The security guide recommends tools such as Argo CD or Flux to review changes to ASO custom resources before applying them.checked 11 Oct 2026
- Installation
- The project identifies Helm as its preferred installation and management method and also documents installation from release YAML.checked 11 Oct 2026
- Integrations
- The project recommends using ArgoCD or Flux to review changes to ASO custom resources before they are merged and applied.checked 10 Oct 2026
- Intended users
- ASO is aimed at users who want to manage Azure resources with Kubernetes tooling and primitives such as kubectl apply.checked 10 Oct 2026
- Kubernetes interface
- ASO provides Kubernetes custom resource definitions and Go API structures for deploying and managing Azure resources.checked 11 Oct 2026
- Prerequisites
- Getting started requires a Kubernetes cluster version 1.32 or later and an Azure subscription.checked 11 Oct 2026
- Project status
- The project describes itself as stable and says it follows the Kubernetes definition of stable.checked 11 Oct 2026
- Purpose
- Azure Service Operator lets users deploy and maintain Azure resources from within a Kubernetes cluster using Kubernetes tooling.checked 11 Oct 2026
- Reconciliation
- ASO uses asynchronous reconciliation and does not block while Azure resources are created.checked 11 Oct 2026
- Resource coverage
- ASO v2 supports more than 150 Azure resources, with more added in each release.checked 10 Oct 2026
- Resource lifecycle
- ASO models Azure resource lifecycle through Kubernetes garbage collection and ownership references.checked 10 Oct 2026
- Security controls
- The security guide recommends controlling installed CRDs, Azure identities and permissions, and Kubernetes identities and permissions.checked 11 Oct 2026
- Security guidance
- The project recommends Azure Workload Identity, namespace-scoped credentials, least-privilege Azure roles, and installing only needed CRDs.checked 10 Oct 2026
- Security limit
- The security guide warns that the RoleAssignment CRD can enable privilege escalation if used carelessly.checked 10 Oct 2026
- Security warning
- The guide warns that the RoleAssignment CRD can enable privilege escalation if it is not used carefully.checked 11 Oct 2026
- Support
- The project directs users to report issues in its GitHub repository or ask questions in the Kubernetes Slack #azure-service-operator channel.checked 11 Oct 2026
- Supported resources
- The project says ASO supports more than 150 Azure resources, with more added each release.checked 11 Oct 2026
Alternatives to Azure Service Operator
- 1
Cloudify
Free planOpen sourceWebAPILinuxmacOS8.4From $395 a month - 2
Terraform
Free planWebAPILinuxmacOS8.0Free plan - 3
Terramate
Free planOpen sourceWebAPIExtensionLinux8.0From $449 a month - 4
AWS CloudFormation
Free planiOSWebAPILinux7.7Free plan - 5
Pulumi
Free planWebAPILinuxmacOS7.4From $40 a month - 6
Oracle Cloud Infrastructure Container Registry
Free planWebAPILinux7.0Free plan