Azure Kubernetes Service (AKS)
Connect your account from Azure Kubernetes Service (AKS) and Wodby will spin up a ready-to-run Kubernetes cluster for you. We will install all necessary infrastructure, so you can deploy your app using one of our stacks in a few clicks.
Specific to this provider
What Wodby sets up on Azure Kubernetes Service
Wodby creates an Azure Kubernetes Service cluster in the subscription you choose after signing in with OAuth. The cluster, its network, and its node pools come from a deployment template and sit in a resource group named after your Wodby organization and region.
Highly available by default
Every AKS cluster Wodby creates is deployed with multi-zone high availability in the region you choose. There is no single-zone variant to select.
Overlay networking with Cilium
New clusters use Azure CNI Overlay, so pods take their addresses from an overlay network and leave the virtual network subnet alone. AKS manages the Cilium dataplane that enforces Wodby's network policies.
Older clusters keep their networking
A cluster still on the kubenet model is not migrated automatically, because changing the networking model of an AKS cluster is a separate and disruptive operation.
One load balancer per cluster
Wodby creates a single load balancer and deploys Envoy Gateway for public app entry points. It relies on the metrics server AKS already includes and turns native Azure monitoring off at creation.
Volumes on Azure Managed Disk
Persistent storage is Azure Managed Disk. A new block storage volume is created for every persistent volume claim, on the default storage class unless another one is selected.
Read the Azure guide for requirements, setup steps, and limits.
Infrastructure we install and maintain
A cluster ready to run your apps
Wodby installs and connects the services for app traffic, resource monitoring, and provider integrations. Start deploying with these essentials in place, and keep them and the Kubernetes version current with Wodby.
Application routing
Publish HTTP and HTTPS endpoints for your apps. Wodby configures the gateway and routes requests to the appropriate service.
- Envoy Gateway
Know how your cluster is performing
View CPU, memory, and storage metrics in Wodby to understand resource usage and investigate capacity issues without assembling your own monitoring stack.
- Monitoring
- Node exporter
- Kubernetes state metrics
Keep your cluster current with less manual work
Wodby upgrades its infrastructure and the infrastructure app stacks automatically, and can upgrade the Kubernetes version too, each with its own version policy and maintenance window. You choose what may change and when, and every upgrade is a task you can follow.
Automatic infrastructure upgrades
Keep Wodby's cluster networking and routing setup current. Enable automatic upgrades and choose which patch, minor, and major changes your cluster may receive.
Automatic infrastructure app updates
Update gateway, monitoring, and controller stacks automatically with their own version policy, including newer revisions of the same version.
Automatic Kubernetes upgrades
Turn automatic upgrades on and Wodby moves the cluster to new Kubernetes patch releases in your maintenance window, while the provider keeps its system components current. They are off by default, because each upgrade replaces the nodes and restarts every pod. You can also review the upgrade plan and start one yourself.
Maintenance on your schedule
Set separate weekdays, hours, and time zones for automatic infrastructure, infrastructure app, and Kubernetes upgrades, so routine maintenance starts when it suits your team.
Reviewable, traceable updates
Review infrastructure app changelogs, Kubernetes upgrade plans, and available release notes. Follow upgrade tasks, retry failed operations, and receive success or failure emails for automatic infrastructure and Kubernetes upgrades.
App environment network isolation
On supported clusters, network policies isolate incoming traffic between app environments while keeping services in the same environment connected.
Need more capacity? On supported scalable managed clusters, set minimum and maximum node counts and let the provider's autoscaler adjust capacity to workload demand. Explore cluster scaling →
How cluster updates work →Budget self-hosted Kubernetes on one server
Azure offers VMs that can be used for a single-server self-hosted Kubernetes setup, which means you can connect one VM and avoid the extra managed Kubernetes overhead around the control plane, cloud load balancer, and block storage. The tradeoff is less flexibility and no Kubernetes scaling compared to a managed cluster, but it can be a good fit for smaller workloads and lower budgets. Read more on the self-hosted Kubernetes page.
Popular stacks
Browse common Wodby stacks and open the stack page for setup, services, integrations, and deployment options.
Prefer not to use your own cloud account or server?
If you want the Wodby Kubernetes workflow without a provider account or server of your own, deploy with Wodby Cloud. It gives you the same managed stacks and deployment model without requiring a cluster in your own cloud account or on your own server.
No separate provider account
Start deploying without creating and wiring AWS, GCP, Azure, DigitalOcean, or dedicated server infrastructure first.
Less infrastructure hassle
Wodby provides the cluster and platform foundation so your team can focus on applications instead of setting up and owning the infrastructure itself.
Simple pay-as-you-go model
Wodby Cloud pricing provides a simpler way to get started with a managed Kubernetes environment and predictable platform costs.
Deploy on Azure Kubernetes Service (AKS) with Wodby
Launch a production-ready environment faster with Wodby-managed infrastructure, deployment workflows, and application stacks.