Job Description:
You'll be building a new AKS cluster end to end to enable a re-IP Addressing programme.
There's an existing estate of multiple Legacy clusters across dev, pre-prod, staging and production.
They grew without a consistent engineering approach, so expect manual config, partial automation and mixed Terraform.
You'll start with discovery across the clusters, namespaces, pipelines, repos, Terraform and Helm dependencies, then define the target design.
From there you'll write the Terraform, build or update the deployment pipelines, work through the Kubernetes version uplift and vulnerability backlog, plan the re-IP sequencing and migrate workloads across to the new cluster.
The brief is a working cluster to deadline, not a gold plated long term platform.
You'll be self sufficient, own it from discovery to implementation and document as you go.
Key skills:
- Hands on AKS, including building a new cluster end to end across multiple environments
- Kubernetes version upgrades, handling deprecated APIs, add-ons and dependency updates
- Production Terraform for AKS from scratch (azurerm provider, modules, remote state)
- Azure networking and IP Addressing: VNet/subnet design, CIDR planning, Azure CNI (incl. Overlay), private clusters, NSGs, UDRs, DNS, private endpoints
- Azure DevOps YAML pipelines or GitHub Actions, including variable groups and Key Vault integration
- Helm packaging and chart updates as part of version remediation
- Migrating workloads from Legacy clusters and planning cutover
Desirable:
- AKS security hardening, ACR, Key Vault CSI driver, ingress, Azure Monitor/Prometheus/Grafana, CKA/AZ-104/AZ-400