zenkubernetes
Learning pathLessonsPractice studioGet the pack
Open practice studio ↗
Foundations
What is Kubernetes?
Setting up for k8s development
The Main Pillars of Kubernetes
Workload types
Creating our first cluster
Core Concepts
Deploying applications
Declaring services
Set up external access
ConfigMaps & Secrets
Debugging & Troubleshooting
Liveness & Readiness Probes
Scaling applications
Updating applications
Revision histories and rollbacks
Application projectPRO
Your application deployment projectBuild and containerize your applicationPackage and deploy with HelmVerify your deployment and hand it over
Troubleshooting practicePRO
Lab: the release that never startsLab: healthy Pods, unreachable applicationLab: configuration blocks startupLab: running does not mean readyLab: recover a failed release
Back at workPRO
Your workplace field guide
Lesson 01

What is Kubernetes?

~3 min read

Your code has to run somewhere

On your laptop, you start an application and send it a request. At work, that application may need several copies, a stable address, configuration, and a way to recover when a machine or process fails.

Kubernetes coordinates those pieces. You describe the state you want, such as two copies of an application, and its controllers keep working toward that state. Application bugs and release compatibility still need your attention.

The map you need as a developer

  • A Pod runs your application container.
  • A Deployment manages replaceable Pods and application updates.
  • A Service provides a stable address and selects the Pods that can receive traffic.
  • An Ingress controller uses routing rules to get external HTTP requests to a Service.

Follow a request: browser → Ingress → Service → ready Pod → application. When a release fails, this map helps you narrow down where to look.

What you will practice

First, inspect and change resources in a browser simulator. Then connect an application project and diagnose five independent incidents in the paid practice pack. Your aim is to understand your application's deployment and give your platform team a useful investigation when you need help.

No installation is required for the browser exercises. Each lesson starts with its own prepared cluster, so you can explore without breaking the next lesson. Use Reset to return to the starting state. Progress is saved in this browser.

Kubernetes originated at Google and is a graduated project of the Cloud Native Computing Foundation. You do not need to learn its entire ecosystem to follow this course.

Should you use it?

If your team already uses Kubernetes, understanding its application workflow is useful. For a new project, it is a tradeoff: managed application platforms or simpler container hosting may meet your needs with less operational work.

Managed Kubernetes reduces some cluster-management work; your team still owns application configuration, release safety, and day-to-day operations. This course concentrates on that application-facing layer.

NextSetting up for k8s development →