I just wanted to emphasise that when you list a pod the resource type that comes back is PodList and when we created our pod it was just Pod. When we list pods, kubectl just sends a HTTP GET request instead of POST because we don't need to submit any data apart from headers:Īnd here's the HTTP 200 OK with JSON file that contains all information about all pods from default's namespace: Pcap: listing_pods.pcap (use http filter on Wireshark) Notice that master node replies with similar data with the additional status column because after pod is created it's supposed to have a status too.

Then, Kubernetes master (API) responds with HTTP 201 Created to confirm our pod has been created: You can even expand it if you want to but I didn't to keep it short. Pcap: creating_pod.pcap (use http filter on Wireshark)īehind the scenes, kubectl command sent an HTTP POST with our YAML file converted to JSON but notice the same thing was sent (kind, apiVersion, metadata, spec): I used a proxy so we don't have to worry about TLS layer and focus on HTTP only. I'll show you on Wireshark the communication between kubectl client and master node (API) for each of the above commands.

What happens when we create, list and delete pods under the hood? More specifically on the wire. This article answers the following question: Exploring Kubernetes API using Wireshark part 2: NamespacesĮxploring Kubernetes API using Wireshark part 3: Python Client API Quick Intro

Wireshark filter http json