I am trying to create an Azure Kubernetes - AKS for production workload.
May be I am misinterpreting the term 'Calico network policy is recommended for dev/test configuration.' is it mean i should NOT use Calico for Production workload AKS?
I am trying to create an Azure Kubernetes - AKS for production workload.
May be I am misinterpreting the term 'Calico network policy is recommended for dev/test configuration.' is it mean i should NOT use Calico for Production workload AKS?
Copyright © 2021 Jogjafile Inc.

Calico network policy is suitable for production workloads on AKS. Calico provides a richer feature set, including support for Windows nodes and supports Azure CNI as well as Kubenet.
Calico is widely used in production environments. The note in the Azure interface suggesting that Calico is recommended for dev/test configurations could be based on its ease of setup and management.
If you are planning to go ahead with Calico for your production setup, you can go ahead without any hesitation.
Azure suggests Azure CNI as a default option for production Kubernetes clusters due to its seamless integration with Azure's native virtual networking environment. Obviously because it's from azure. It's just that if you use Azure Container Networking Interface (CNI), with Azure option, every pod gets an IP address from the subnet and can be accessed directly.
Check out these documents for better clarity on Calico and Azure CNI and decide which suits your need based on your current environment.
References: