Kubernetes

Azure AKS

AKS is the natural choice for businesses already on Microsoft 365 and Azure: identity comes from Entra ID, monitoring from Azure Monitor and networking ties into existing VNets and ExpressRoute.

We deploy AKS with Bicep or Terraform, Entra ID RBAC on the cluster, Azure CNI Overlay for address efficiency and either NGINX or Application Gateway ingress depending on WAF needs.

At a glance

ProvisioningTerraform, Bicep
NetworkingAzure CNI, CNI Overlay, kubenet (legacy)
IngressNGINX, Application Gateway Ingress Controller, Application Gateway for Containers
IdentityEntra ID RBAC, Workload Identity

What RackLedge does

How we work

Every cluster we build starts from Git. Infrastructure as code creates the cluster, Flux or Argo CD reconciles everything inside it, and no change reaches production without a pull request. That is what makes a rebuild after a bad day a matter of hours instead of weeks.

Operations are the product: monitoring with alerts that mean something, backups of cluster state and persistent volumes, upgrades on a quarterly cadence and an on-call engineer who already knows the environment. We run production Kubernetes for our own platforms, so the runbooks are ones we use ourselves.

We are honest about fit. A handful of stable services on a couple of VMs does not need Kubernetes, and we will say so. Teams that ship weekly, need to scale or run many services get real value from it.

Related services

More on kubernetes

Frequently asked questions

Can AKS run Windows containers?

Yes, with Windows node pools. Useful for .NET Framework apps that cannot move to Linux yet.

Need a hand with this?

Tell us what you are running and what is slowing you down. You get a straight assessment and a plan, with no obligation. Support desk is staffed 24/7.

Get in touch