AKS — DNS Testing in Kubernetes

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
name: dnsutils
namespace: default
dnsPolicy: Default
— name: single-request-reopen
— name: ndots
value: “5”
— name: dnsutils
image: k8s.gcr.io/e2e-test-images/jessie-dnsutils:1.3
— sleep
— “360000”
imagePullPolicy: IfNotPresent
restartPolicy: Always



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store