Azure Kubernetes Service (AKS)

Azure Kubernetes Service, AKS, gives you a managed container platform for modern applications. Run it on Azure Local and your containers run on your own hardware, close to your data and your machines, with the same Kubernetes tooling and Azure integration you'd get in the public cloud.

How you put it to work

You add AKS to your Azure Local platform and deploy containerized applications with the tooling your team already uses. For AI, you set up Foundry Local on AKS with GPU capacity, so models run on your own hardware. Everything is managed as code and monitored centrally, so it stays something your own team can run, not a project only we understand.

What is it, exactly

Azure Kubernetes Service is Microsoft’s managed Kubernetes. On Azure Local it runs as an Arc-enabled cluster on your own hardware, with the same APIs and tooling as in the public cloud. It supports GPU nodes for AI workloads, and you deploy with the pipelines your team already uses. What that looks like in practice, from setup to deployment, is in the blogs below.

‍

See it run before you invest

Run a real workload with your own data, in our Technology Experience Center or on your own site. Seeing it work beats any presentation.

Questions

Frequently asked questions

Contact us
01

What's the difference between AKS in Azure and AKS on Azure Local?

AKS in Azure runs your Kubernetes clusters in an Azure region, on infrastructure Microsoft manages. AKS on Azure Local runs them on your own hardware, managed from the same Azure portal with the same Kubernetes APIs. You choose per application: Azure for scale, Azure Local when the data or the machines are on-site. We've run Kubernetes on this platform since the Azure Stack HCI days and have written about it in depth on our blog.

‍

02

Can we run AI models on AKS with our own GPUs?

Yes. AKS on Azure Local supports GPU nodes, so you can run AI models in containers on your own GPUs. With Foundry Local on Azure Local, Microsoft provides a ready-made way to serve those models on that platform, managed through Azure Arc.

‍

03

Do our developers need different tooling?

No. AKS on Azure Local runs standard Kubernetes, so kubectl, Helm and your existing CI/CD pipelines work the same way as with AKS in Azure. Developers deploy to an on-premises cluster the same way they deploy to the cloud.

‍

04

When do containers make more sense than virtual machines?

It depends on how your applications are built. Modern applications that are split into services and updated often get the most from containers: faster deployments, better use of hardware and easier scaling. Older applications built for a single server usually stay on virtual machines, and Azure Local runs both side by side.

‍

Other solutions

Datacenter modernization

Hardware up for renewal and VMware costs climbing? Modernize instead of renewing the same setup.

Artificial Intelligence

Run AI on GPUs inside your own datacenter, so your data stays where you put it.