Listed as Free on Udemy when checked on 6 November 2026. No coupon or subscription trial is required for the listed lessons. Enrollment needs a Udemy account; availability can change.
About this course
Starting a container and keeping an application running are different jobs. A container gives you a way to run a packaged application. An orchestrator adds a way to describe where copies should run and what should happen when one disappears. That distinction is the starting point of Srinath Challa’s free introduction to Kubernetes.
The five sections move from orchestration and cluster architecture to setup demonstrations, Pods, and controllers. The 13 listed videos run for about three hours and 41 minutes. Treat the installation recordings as examples from 2021. The course is useful for learning how the parts fit together, while the setup commands and hosted lab availability need a current check before you follow along.
| Official course | Kubernetes: Getting Started |
|---|---|
| Created by | Srinath Challa |
| Platform | Udemy |
| Language | English |
| Level | Beginner |
| Listed duration | 221 minutes; 13 lectures across 5 sections |
| Completion terms | Not included with a new free enrollment |
What you’ll learn
Explore the control plane and worker nodes, then see how Kubernetes runs containers inside Pods. Follow the Pod demo and compare the roles of a ReplicationController, a ReplicaSet, and a Deployment. The listing introduces a NodePort example; whether an application is reachable from outside the cluster depends on the network and its access rules.
Skills you’ll gain
- Container orchestration
- Cluster architecture
- Pod manifests
- Labels and selectors
- ReplicaSets
- Deployment rollouts
Separate the request from the running workload
When you read a small manifest, identify the kind of object first. Then find the name, labels, and the part that describes what should run. A Pod is the unit Kubernetes schedules. The container image is an input to the Pod; it is not the Pod itself. Write down which detail you expect to see once the workload starts, such as the number of ready copies.
Use the controller lessons to explain why deleting a Pod has different effects depending on who manages it. A standalone Pod has no ReplicaSet maintaining a desired number of copies. When a ReplicaSet owns a matching Pod and fewer copies are running than requested, the controller can create a replacement. A Deployment adds a way to update that set over time. Work with the Deployment when it owns the ReplicaSet.
Use an isolated cluster for practice
For separate practice, use a current local Kubernetes environment and a throwaway namespace. Start a small web workload through a Deployment with one replica. Inspect the Pod and the Deployment status, then change the desired count to two. Check both the requested count and the ready count. They need not match immediately, so observe whether the second Pod is still starting instead of assuming scaling failed.
The course shows older paths for setting up a cluster, including kubeadm. Kubernetes removed the built-in dockershim integration in version 1.24. Docker can still build usable container images, but the node needs a compatible runtime setup. If you want to build a cluster, follow the current instructions for your Kubernetes release and platform. A working training cluster still leaves separate decisions about production access, networking, upgrades, and maintenance.
Watch what changes during an update
Once both copies are ready, change a harmless part of the Pod template in the local practice Deployment. Watch the old and new ReplicaSets during the rollout. If the change stalls, read the events and check the Pod before changing more settings. To view the app in a browser, use local port forwarding for the practice run and keep the sample service off the public internet.
A Service gives clients an address for reaching a set of matching Pods even as individual copies change. Keep that distinction in mind when reviewing the older NodePort demo. Creating a Service and making it reachable from a particular network are separate steps. For local study, first verify that you can reach the workload from your own machine.
Finish by removing the resources you created in the throwaway namespace. Save your observations about which objects appeared or changed during scaling and during the template update. If you can explain why those two actions produce different results, you have a useful foundation for reading the more complex manifests that show up in team projects.
Related courses for your next step
- Compare another approachFree Docker Containers Course
Focus: Dockerfile instructions · Image builds
Beginner
- Add a related skillFree Bash Scripting Course
Focus: Script setup · Interpreter selection
Beginner
Compare course focus, level and study time
| Course | Level | Focus | Study time |
|---|---|---|---|
| This course — Free Kubernetes Basics Course: Understand Pods and Deployments | Beginner | Container orchestration · Cluster architecture · Pod manifests | 221 minutes (Udemy listing) |
| Free Docker Containers Course: Images, Storage, and Networking | Beginner | Dockerfile instructions · Image builds · Container startup | 77 minutes (Udemy listing) |
| Free Bash Scripting Course: Write Your First Linux Script | Beginner | Script setup · Interpreter selection · Shell builtins | 44 minutes (Udemy listing) |
Frequently asked questions
Does the free course include the instructor’s YAML files and slides?
The instructor places those materials in the separate Kubernetes Made Easy course.
Do I need a paid cloud account?
You can watch the listed free lessons without buying a cloud plan. A local practice cluster is a separate option; cloud resources may carry charges if you choose to use them.
Can I use the setup recordings to build a production cluster today?
Use them to understand the roles of the components. Use current Kubernetes installation guidance for your version and platform, and plan production security and operations separately.
Questions & discussion
Share a useful question or correction. Comments appear after moderation. Please avoid personal or sensitive information.