Nerd For Tech
Published in

Nerd For Tech

Exploring Kubernetes Node Architecture.

Photo by Danny Saltaren on Unsplash

Pods, Nodes, and Containers

Kubelet and a Kube-proxy

On those Nodes, you also have Kubelet and a Kube-proxy service running. the Kubelet is responsible for launching the pods. It’s going to connect to the master Node to get the information.


The easiest way to remember how a Service works is just to imagine yourself as a Load Balancer 😅. Your service can be the ELB (Elastic Load Balancer) on AWS. This Elastic Load balancer on AWS is going to be publicly available so that clients from the internet can connect to your load balancer and your load balancer is then going to forward traffic to your Kubernetes cluster which is going to have all the Nodes listed and the traffic is all going to arrive at iptables.

To translate this to a Yaml file:

apiVersion: v1kind: Podmetadata:name: hello-world.example.comlabels:app: hello-worldspec:containers:- name: docker-demoimage: thecraftman/docker-demoports:- name: python-portcontainerPort: 3000

If you would have two containers, you will just have a spec with two containers.


Enjoyed the read? Leave some ‘claps’ below so others can find this post 🙂



NFT is an Educational Media House. Our mission is to bring the invaluable knowledge and experiences of experts from all over the world to the novice. To know more about us, visit

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