Kubernetes on Microsoft Azure (AKS)¶
3 days · 9:00–16:00 Intermediate 15 hands-on labs on-site or remote · English / Polish
Build, secure and operate a production-style platform on Azure Kubernetes Service. Participants create one cluster on day one and extend it lab by lab – networking, ingress with the Gateway API, TLS, identity, secrets, storage, monitoring, GitOps and CI/CD – ending with a troubleshooting challenge.
Who it's for¶
DevOps and platform engineers, cloud architects and developers who run – or are about to run – workloads on AKS.
Prerequisites: basic Kubernetes (pods, deployments, services), Linux shell, an Azure subscription with Owner rights on a resource group and quota for ~8 vCPUs.
What you will be able to do¶
- Design an AKS cluster: tiers, versions, node pools, Azure CNI Overlay with Cilium
- Expose applications with Gateway API – App Routing and Application Gateway for Containers – with automatic TLS
- Lock down traffic with network policies and access with Entra ID, Azure RBAC and no local accounts
- Give workloads secretless access to Azure with Workload Identity and Key Vault
- Run stateful workloads on Azure Disk and Azure Files
- Observe and scale: Container insights, managed Prometheus, HPA, cluster autoscaler
- Deliver changes with GitOps (Flux) and CI/CD pipelines in Azure DevOps or GitHub Actions
- Troubleshoot the most common pod, network and platform problems
Agenda¶
| Topic | Lab |
|---|---|
| Containers, images, Azure Container Registry | LAB01 |
| AKS overview: tiers, versions, capacity, node OS | |
| Creating clusters with the CLI and IaC | LAB02 |
| Network architecture: CNI Overlay, Cilium, API server access | |
| Services, Azure Load Balancer, egress | LAB03 |
| Topic | Lab |
|---|---|
| Ingress in 2026: Gateway API and App Routing | LAB04 |
| TLS with cert-manager | LAB05 |
| Application Gateway for Containers | LAB06 |
| Network policies, Pod Security, Azure Policy, Defender | LAB07 |
| Kubeconfig, Kubernetes RBAC | LAB08 |
| Entra ID, Azure RBAC, local accounts | LAB09 |
| Workload Identity and Key Vault | LAB10 |
Environment¶
Labs run in Azure Cloud Shell – no local installation needed. One cluster (2–3 small nodes) is created in LAB02 and reused until the end; stopping it overnight keeps costs to a few euros per day.