DH2i Blog Article

Introducing DxOperator v2: Smarter, Safer, More Adaptable SQL Server on Kubernetes

Don Boxley Jr
/
March 17, 2026

Running Microsoft SQL Server on Kubernetes is no longer a fringe use case, but doing it well still requires careful orchestration. High availability, rolling updates, networking, and lifecycle management all become more complex once SQL Server is containerized. That’s exactly why DH2i created DxOperator in the first place, and it has since garnered the reputation as Microsoft’s preferred SQL Server Operator for Kubernetes.  

Now, DH2i is taking a major step forward in flexibility, automation, and operational simplicity with the release of DxOperator v2. 

DxOperator v2 builds on the proven foundation of the original release, while introducing key architectural and usability improvements that make SQL Server Availability Groups on Kubernetes easier to manage, easier to update, and easier to adapt and scale over time. 

A Quick Recap: DH2i’s SQL Server Operator for Kubernetes 

DxOperator is an included feature of DxEnterprise High Availability software. It was created to automate the deployment and lifecycle management of SQL Server Availability Groups on Kubernetes. It uses Kubernetes custom resources to allow users to define their exact AG specifications (e.g. number of replicas, replication mode, storage, networking, and more) and then automates the deployment process while making sure state is achieved and maintained. 

What’s New in DxOperator v2 

DxOperator v2 focuses on one clear goal: advancing operational efficiency, reliability, and lifecycle automation for SQL Server Availability Groups on Kubernetes. The result is a far more capable software solution that handles scaling, updates, and connectivity with less manual intervention, while maintaining the high-availability guarantees required for enterprise SQL Server deployments. 

Scale Up and Scale Down SQL Server Availability Groups 

With DxOperator, administrators could expand an Availability Group by adding replicas. DxOperator v2 takes scalability to the next level by supporting both scale-up and scale-down operations. Users can increase or shrink the number of pods in an Availability Group, with DxOperator v2 automatically de-configuring and removing replicas from a running cluster as needed.  

Why it matters:
This makes SQL Server on Kubernetes far more adaptable. Whether you’re reducing costs, rebalancing workloads, or resizing for changing demand, v2 allows Availability Groups to evolve without downtime or fragile manual steps. 

Automated Rolling Updates for Container Images 

Updating SQL Server or DxEnterprise container images in v1 was a tedious, manual process in which users had to: 

  1. Configure the new image
  2. Delete one pod
  3. Wait for it to be recreated
  4. Verify health
  5. Repeat for each replica 

DxOperator v2 introduces automated rolling updates to simplify this process immensely. 

Administrators can now instruct DxOperator to automatically delete and recreate pods one at a time using a new container image, and they still have the ability to retain manual control if desired. Kubernetes and DxEnterprise’s underlying high availability engine work together to ensure uptime is maintained throughout the process. 

And for added clarification, DxOperator does not auto-detect or auto-pull new images. The administrator remains fully in control of which images are deployed — v2 simply makes the rollout safer and dramatically faster. 

Why it matters:
Rolling updates are a foundational Kubernetes capability. Bringing them natively into SQL Server Availability Groups reduces risk, saves time, and aligns database operations with modern DevOps practices.  

Flexible, Per-Instance Service Templates 

Exposing SQL Server to applications requires carefully configured network services. Kubernetes clusters are intentionally locked down by default, relying on services and load balancers to allow inbound connectivity. 

DxOperator v1 offered basic boilerplate service creation that was sufficient for some environments, but limiting in others, especially across cloud providers. 

DxOperator v2 introduces fully configurable service templates, allowing administrators to define load balancers and network services in full detail and have them automatically created per pod in an Availability Group. 

Why it matters:
Different environments require different networking configurations. With v2, SQL Server connectivity can be tailored precisely to your cloud, on-prem, or hybrid setup — without post-deployment manual fixes.  

A Redesigned Custom Resource Built on StatefulSets 

One of the biggest architectural improvements in DxOperator v2 is invisible at first glance, but hugely impactful. 

The custom resource definition (CRD) has been redesigned to use Kubernetes StatefulSets for pod management. 

In the v1 release, DxOperator created and managed each SQL Server pod individually. While flexible, this required DxOperator itself to handle many low-level details such as ordering, storage attachment, and updates. 

In v2, DxOperator delegates those responsibilities to Kubernetes by creating a single StatefulSet. 

Why it matters:
StatefulSets are purpose-built for stateful workloads like databases. They handle pod identity, persistent storage, and rolling updates natively — and they do it extremely well. By leaning into the existing core competencies of Kubernetes, DxOperator v2 becomes simpler, more reliable, and easier to maintain over time.  

Why DxOperator v2 Is a Big Step Forward 

DxOperator v2 isn’t just an incremental update — it’s a maturation of how SQL Server Availability Groups should run on Kubernetes: 

  • More control over scaling and networking
  • Less manual work during upgrades and changes
  • Better alignment with native Kubernetes capabilities
  • Stronger foundations for long-term operability 

For teams running production SQL Server workloads in containers, v2 reduces operational friction while increasing confidence and flexibility.  

Getting Started with DxOperator v2 

Whether you’re deploying new Availability Groups or modernizing existing ones, v2 provides a cleaner, more powerful operational model to unlock the benefits of containerization for critical SQL Server databases. 

To learn more, explore the DxOperator product pagedocumentation, and quick-start resources, or reach out to DH2i for a free demo to see DxOperator v2 in action. 

If you’re interested in learning more about DH2i’s approach to smart high availability technology, get signed up for a one-on-one demo today.

The author
Don Boxley Jr

Native. Containerized. Anywhere in Between.

DH2i gets you closer to zero downtime.