What is the main purpose of the repo?

This repo will discuss how to deploy Cilium on AKS clusters with Terraform:

• Isovalent Enterprise for Cilium in Azure Marketplace (Overlay mode).
• Isovalent Enterprise for Cilium in Azure Marketplace (Dynamic IP allocation mode).
• Isovalent Enterprise for Cilium in Azure Marketplace (Overlay Mode) (Azure Linux as the host OS).
• Isovalent Enterprise for Cilium in Azure Marketplace (Dynamic IP allocation mode) (Azure Linux as the host OS).
• Isovalent Enterprise for Cilium in Azure Marketplace on a private AKS cluster (Overlay mode).
• Isovalent Enterprise for Cilium in Azure Marketplace on a private AKS cluster (Dynamic IP allocation mode).
• Bring your own CNI (BYOCNI) in IPv4 and Dual Stack mode.
• Bring your own CNI (BYOCNI) with Azure Linux as the host OS in IPv4 and Dual Stack mode.
• Bring your own CNI (BYOCNI) with Azure Linux version 3.
• Bring your own CNI (BYOCNI) for a Private AKS cluster.
• Bring your own CNI (BYOCNI) with ARM based nodepools support.
• Bring your own CNI (BYOCNI) with KEDA (Kubernetes Event Driven Autoscaler) support

You will also get to learn how to deploy an AKS cluster using the other AKS CNI's like:

• Kubenet in IPv4 and Dual Stack mode.
• Azure CNI powered by Cilium (Overlay Mode) with Cilium as the Network Policy in IPv4 and Dual Stack mode.
• Azure CNI powered by Cilium (Dynamic IP allocation) with Cilium as the Network Policy.
• Azure CNI powered by Cilium (Overlay Mode) with Azure Linux as the host OS in IPv4 and Dual Stack mode.
• Azure CNI powered by Cilium (Dynamic IP allocation) with Azure Linux as the host OS.
• Azure CNI powered by Cilium (Overlay Mode) for a Private AKS cluster.
• Azure CNI powered by Cilium (Dynamic IP allocation) for a Private AKS cluster.
• Nodepools in Different Availability Zones (with Azure CNI powered by Cilium as the choice of CNI).
• Azure CNI Overlay in IPv4 and Dual Stack mode .
• Azure CNI with Azure NPM as the network policy.
• Azure CNI with Calico as the network policy.

Ensure you have enough quota

Go to the Subscription blade, navigate to "Usage + Quotas", and make sure you have enough quota for the following resources:

• Regional vCPUs
• Standard Dv4 Family vCPUs