Ambassador Labs

Code, ship, and run apps for Kubernetes faster and easier than ever — powered by Ambassador’s industry-leading developer experience.

Follow publication

GETTING EDGY VIDEO SERIES

Getting Edgy: Clusters, Nodes, Pods, and Containers — Oh My!

What’s the difference between a cluster, a node, a pod, and a container in Kubernetes?

Kelsey Evans
Ambassador Labs
Published in
1 min readJan 28, 2020

--

Kubernetes introduces a lot of new vocabulary. Today, we will break down Kubernetes into several layers of abstraction from smallest to largest.

Container

A container bundles code and dependencies into one standard uniit of software, called a “container image”. This container image isolates code from the environment allowing the application to run consistently regardless of infrastructure or computing environment.

Pod

The first layer of Kubernetes-native abstractions, a pod is a way to bundle up and package containers into one logical grouping that represents a process in your cluster. A pod can have one or more containers that will all share the same environment.

Node

A node is the actual machine your pods are running on. They can be bare metal or virtual machines.

Cluster

A cluster is a grouping and management abstraction for nods. All of the orchestration and networking magic happens at the cluster level.

Learn More

Subscribe to the Ambassador YouTube Channel to get updates about new weekly videos!

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

--

--

Published in Ambassador Labs

Code, ship, and run apps for Kubernetes faster and easier than ever — powered by Ambassador’s industry-leading developer experience.

No responses yet

Write a response