Migrating to Azure Kubernetes Service (AKS)

Motivation

The current Bicep template deploys workloads using Azure Container Apps, but our requirements now need greater control, flexibility, and alignment with enterprise standards.
Migrating to Azure Kubernetes Service (AKS) will provide better networking, security, scalability, and integration with existing DevOps and Kubernetes-based tooling.

Requirements

A list of requirements to consider this feature delivered

• Replace Azure Container Apps with Azure Kubernetes Service (AKS)
• Support deployment to an existing or newly created AKS cluster
• Deploy workloads using Kubernetes manifests or Helm
• Integrate with Azure Container Registry (ACR)
• Support managed identities, secrets, and environment configuration
• Be compatible with CI/CD-based deployments

Tasks

To be filled in by the engineer picking up the issue

• Design AKS-based architecture
• Update Bicep template to provision or reference AKS
• Migrate application deployment to Kubernetes
• Update documentation and deployment steps

Start by locating the current Bicep template and the Azure Container Apps deployment it provisions. Define the AKS architecture and decide how existing or new clusters, Kubernetes manifests or Helm, ACR, identities, secrets, configuration, and CI/CD fit together. Done means the workloads deploy through AKS and the deployment documentation is updated.