In order to better understand the implications of DNS resolutions inside a cluster, we provided some packet capture on the resources deployed and analyze them with Wireshark.

For testing purposes, we used the following resources:

1 Node — AKS Public Cluster

- kubectl krew — With sniff plugin for deployment…

--

--

az aks disable-addons -a monitoring -n MyExistingManagedCluster -g MyExistingManagedClusterRG

Re-enable the monitoring AddOn with the following command: az aks addon enable –addon –name — resource-group — workspace-resource-id

--

--