Blog on Azure Service Operator

ASO v2.21 Release Notes

Mon, 31 Aug 2026 00:00:00 +0000

We’re excited to announce the release of Azure Service Operator v2.21.0! This release completes the rollout of smarter deletion, removes retired Redis Enterprise API versions, expands support for Entra ID and several Azure services, and adds more control over operator security and authentication.

🎇 Headline Features

The migration to smart deletion prechecks is now complete. ASO checks whether a resource or its parent still exists before issuing a DELETE to Azure, avoiding unnecessary calls and reducing error churn when you remove large resource graphs. This release enables the precheck for the remaining API groups, including compute, containerinstance, datafactory, dbforpostgresql, devices, insights, keyvault, machinelearningservices, network, redhatopenshift, resources, servicebus, and storage.

Breaking Changes for Redis Enterprise

Wed, 01 Jul 2026 00:00:00 +0000

If you manage RedisEnterprise or RedisEnterpriseDatabase resources with ASO, this post is for you. In ASO v2.21 (scheduled for August 2026), we will remove the v1api20210301 and v1api20230701 versions of both resources. You’ll need to move your YAML to a newer API version before upgrading.

This change is driven by an upstream Azure decision: Azure Cache for Redis Enterprise is being retired in favour of Azure Managed Redis, and the older ARM API versions cannot manage the new product.

ASO v2.20 Release Notes

Wed, 24 Jun 2026 00:00:00 +0000

We’re excited to announce the release of Azure Service Operator v2.20.0! This release extends simplified versioning to four more resource groups, rolls smart deletion prechecks out across more than twenty groups, adds a way to resolve Azure resource names from ConfigMaps at reconciliation time, and introduces support for Microsoft Foundry projects.

🎇 Headline Features

Four more resource groups now support simplified API versioning: compute, app, eventgrid, and datafactory (#5348, #5342, #5344, #5343). You can now use resources in these groups with the new v prefix (e.g. v20250701 instead of v1api20250701), while the legacy v1api versions remain available for backward compatibility. We strongly recommend using the new version format wherever it’s available, as it sorts correctly for kubectl get (see #4147) and the v1api versions will eventually be removed after a deprecation period.

ASO v2.19 Release Notes

Fri, 24 Apr 2026 00:00:00 +0000

We’re excited to announce the release of Azure Service Operator v2.19.0! This release expands simplified versioning to six more resource groups, adds new API Management and Cassandra resources, improves reconciliation performance, and tightens security by converting secret-bearing fields to proper secret references.

🎇 Headline Features

Six more resource groups now support simplified API versioning: alertsmanagement, appconfiguration, apimanagement, dbformysql, synapse, and web. You can use all resources in these groups with the new v prefix (e.g. v20250701 instead of v1api20250701), while the legacy v1api versions remain available for backward compatibility. We recommend you using this new format for groups that support it. We will continue rolling out this version style to all groups over the next release or two.

ASO v2.18 Release Notes

Wed, 18 Feb 2026 00:00:00 +0000

We’re excited to announce the release of Azure Service Operator v2.18.0! This release adds new AKS preview API support, expands simplified versioning to storage resources, strengthens reconciliation checks, fixes Helm configurability issues, and updates a broad set of dependencies and tooling.

🎇 Headline Features

The storage group now supports simplified API versioning. You can use all storage resources with the new v prefix, while the legacy v1api versions remain available for backward compatibility. This continues our transition toward simplified versioning across all resource groups (see #4831 for more detail).

Why record our tests?

Tue, 03 Feb 2026 00:00:00 +0000

Azure Service Operator v2 uses recorded HTTP interactions for many of its integration tests. This blog post explains why we do this, and the benefits it brings.

Early in the development of ASO v2, we ran into problems with some of our end-to-end tests.

Sometimes a test that successfully worked one day would fail the next. We’d spend time investigating, assuming that this was due to something we’d changed, only to find the failure was due to outside factors.

Developer Talks - Quality of Life Features with Bevan

Fri, 19 Dec 2025 00:00:00 +0000

With the release of ASO v2.17 coming soon, this felt like a great time to go behind the curtain and get a better idea of what us devs have been working on, both landed and upcoming, and how they contribute to a smoother user experience for ASO users.

We’ll go over two exciting features, one landing in v2.17 and one that shipped in v2.16. Alongside our other host of improvements, we hope these features make using ASO that much smoother for our users.

ASO v2.17 Release Notes

Mon, 08 Dec 2025 00:00:00 +0000

We’re pleased to announce the release of Azure Service Operator v2.17.0! This release brings new PostgreSQL and Log Analytics resources, improved secret exports across several services, and the beginning of our transition to simplified API versioning.

Administrative note: This blog post written in early February 2026 and backdated to the actual release date for v2.17.

🎇 Headline Features

Resources introduced in this release are using simplified versioning, as we’re deprecating the v1api prefix (see #4831). We’ve laid the foundation for migration to the new versioning style, with batch resources being the first to migrate.

ASO v2.16 Release Notes

Wed, 29 Oct 2025 00:00:00 +0000

We’re excited to announce the release of Azure Service Operator v2.16.0! This release comes with a host of improvements and fixes, along with support being added for some oft-requested resources.

⚠️ Breaking changes

This release includes breaking changes. Please review the breaking changes documentation before upgrading.

🎉 New and improved resource support

New resource support

We’ve added support for three new resources:

Azure Compute Capacity Reservation Groups allowing capacity reservation manifests to be declaratively included alongside VM manifests
- Special thanks to bingikarthik for his contribution!
Managing Azure quotas for Kubernetes native management of Azure quotas
- Special thanks to bingikarthik for his contribution!
NetworkWatchers/flowLogs for management of Network Security Group Flow Logs.

Enhanced resource references

We’ve enhanced existing resource references with additional functionality: