Open amitmavgupta opened 1 year ago
Assigned to take a look . Please respond @paulgmiller @wedaly
I believe this is an Azure Portal display issue (since the output from AKS APIs show network-policy=cilium). Could we please reassign it to someone from Azure Portal to take a look?
@kaarthis could we have some assigned to take a look at this please?
Describe the bug Network Policy is shown as "None" for an AKS cluster on Azure CNI powered by Cilium on Azure Portal
To Reproduce Create an AKS cluster as below
az group create --name nwpluginazurecniciliumoverlay --location francecentral
az aks create -n nwpluginazurecniciliumoverlay -g nwpluginazurecniciliumoverlay -l francecentral \ --network-plugin azure \ --network-plugin-mode overlay \ --pod-cidr 192.168.0.0/16 \ --network-dataplane cilium
Expected behavior Since this is an AKS cluster that is created with network-dataplane as Cilium we would expect that the Azure Portal shows Network Policy as Cilium but that is not the case. It is being shown as None in the Azure portal.
"loadBalancerSku": "Standard", "monitoring": null, "natGatewayProfile": null, "networkDataplane": "cilium", "networkMode": null, "networkPlugin": "azure", "networkPluginMode": "overlay", "networkPolicy": "cilium", "outboundType": "loadBalancer", "podCidr": "192.168.0.0/16", "podCidrs": [ "192.168.0.0/16" ], "serviceCidr": "10.0.0.0/16", "serviceCidrs": [ "10.0.0.0/16" ]
Screenshots As you can see in the screenshot Network Policy is shown as None.
Environment (please complete the following information):
Additional context
@wedaly helped by informing that networkPolicy=cilium as an option was added in API version 2023-02-01. It could be possible that an older API version is being used and not expecting the "cilium" enum for that field.