Translating the features from ACA to AKS

Now that we have decided on AKS and looked at what we need to deploy, we need to understand how our ACA configuration maps to AKS.

ACA configuration for the original use case

For ACA, we had the following configuration set up, as we discussed in Chapter 13, Azure Container Instances – The Next Steps:

• One container app environment per customer, as this will be the “secure boundary” our customers require
• Two container apps per environment, one for the web frontend and one for the API
• Ingress configuration per environment (customer)
• A custom domain for each customer

The use case was extended; we need to make sure we can now run these services on AKS and continue daily operations. We don’t really have new technical requirements but we need to translate exactly what we have here to an Azure Kubernetes configuration.

Azure Kubernetes configuration for an extended use case

Let’...