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 of static compiled tcpdump to desired Pod

- Wireshark

The Pod used for the running queries has been created with the following manifest file:

apiVersion: v1
kind: Pod
metadata:
name: dnsutils
namespace: default
spec:
dnsPolicy: Default
dnsConfig:
options:
— name: single-request-reopen
— name: ndots
value: “5”
containers:
— name: dnsutils
image: k8s.gcr.io/e2e-test-images/jessie-dnsutils:1.3
command:
— sleep
— “360000”
imagePullPolicy: IfNotPresent
restartPolicy: Always

--

--

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

--

--