AKS and our use case

Overall, our use case requires us to use AKS because we need to comply with the following requirements:

• The web frontend relies on the billing statement API.
• The solution (frontend and API) is deployed per customer (single tenant).
• The solution runs 24/7 throughout the month.
• (New) We need to service 25 customers.
• We need a custom domain per customer.
• The billing API and the web frontend have different life cycles.
• The billing API can generate a peak workload, therefore we need scaling.
• (New) New additions to the platform will be containerized.

To implement the infrastructure to fulfill these requirements, we recommend an AKS cluster and the use of namespaces and network policies to create a secure boundary. Additionally, we will use an Ingress controller and Ingress resource to allow the customer to configure the custom domain and provide a certificate for secure traffic.

For security reasons, we also recommended the...