Q&A
Kubernetes for Developers
Cloud-native application development has changed what developers are expected to understand about deploying, scaling and managing software. It is no longer enough to simply write code and hand it off to operations. As more applications move into containers and distributed architectures, developers are increasingly being asked to understand the platforms that keep those applications running reliably.
That is where Docker and Kubernetes come in. Docker gives developers a practical way to package applications and their dependencies into containers, while Kubernetes provides the orchestration layer for deploying, scaling and managing those containers across environments. Together, they have become foundational technologies for teams building modern microservices-based systems.
For developers who have heard the terms but have not yet had time to dig in, the upcoming Kubernetes for Developers session at Visual Studio Live! San Diego 2026 in September is designed as an introductory, practical starting point.
In the session, Dan Wahlin, Principal Cloud Developer Advocate at Microsoft, will explain the role Docker and Kubernetes play in the developer workflow, while breaking down core Kubernetes concepts such as pods, nodes, deployments and services. The goal is to help developers understand not just the terminology, but how these pieces fit together when deploying containerized applications.
"I'm passionate about helping developers understand Kubernetes and how it solves real-world deployment challenges. It can feel overwhelming at first because there are a lot of moving parts, so I enjoy helping people get to that 'aha' moment where the concepts finally click and they can see how Kubernetes fits into their everyday work."
Dan Wahlin, Principal Cloud Developer Advocate, Microsoft
The introductory-level session is scheduled for Thursday, Sept. 17, 2026, from 8 a.m. to 9:15 a.m. as part of the San Diego event.
Dan is set to focus on the practical side of getting started, including the benefits of Kubernetes, the platform's core features and how developers can begin deploying applications to Kubernetes. For attendees who have been meaning to learn more about containers and orchestration but have not yet made the leap, the session offers a guided path into one of the most important areas of modern application development.
We caught up with Dan to learn more about why Kubernetes matters for developers, how it fits into today's cloud-native workflow, and what attendees can expect to take away from the session.
VisualStudioMagazine: What Inspired You to Present on This Topic?
Wahlin: I'm passionate about helping developers understand Kubernetes and how it solves real-world deployment challenges. It can feel overwhelming at first because there are a lot of moving parts, so I enjoy helping people get to that "aha" moment where the concepts finally click and they can see how Kubernetes fits into their everyday work.
For Developers Who Are New to Kubernetes, What Misconception Do You Most Want to Clear Up in This Session?
A common misconception is that Kubernetes is only for large enterprises running massive cloud environments. In reality, developers can learn and use Kubernetes locally with tools like Docker Desktop, minikube, or Rancher Desktop, which makes it much easier to experiment, build confidence, and understand how everything works before moving to production.
How Do You Explain the Relationship Between Docker and Kubernetes in a Way That Clicks Quickly for Beginners?
I usually explain it as Docker builds and runs individual containers, while Kubernetes orchestrates groups of containers at scale. Docker helps you package the application, and Kubernetes helps you deploy, scale, monitor, and keep those containers running reliably across environments. From a visual standpoint, think of Docker containers as the individual musicians in an orchestra, while Kubernetes is the conductor making sure everyone stays in sync, comes in at the right time, and keeps the performance running smoothly even if one player misses a beat.
Which Kubernetes Concept -- Pods, Nodes, or Deployments -- Tends to Be the Most Important for Developers to Understand First?
Pods are usually the best place for developers to start because they are the basic unit that runs one or more containers in Kubernetes. Once developers understand that Pods are where their applications actually run, it becomes much easier to see why Deployments matter, since Deployments manage those pods by handling scaling, updates, and recovery automatically so applications stay available and easier to maintain.
What Is One Practical Example You'll Share to Show How Kubernetes Fits into a Developer's Everyday Workflow?
I'll walk through deploying a simple application locally using Docker Desktop Kubernetes and exposing it with a Service so it can be accessed in the browser. This shows developers how Kubernetes fits naturally into the same workflow they already use with containers, just with more control over scaling and management.
When Developers First Deploy to Kubernetes, What Is the Most Common Mistake They Make?
One of the most common mistakes is treating Kubernetes exactly like Docker and assuming a container will behave the same way without understanding Pods, Services, and configuration. Another frequent issue is missing or incorrect labels and selectors, which can prevent Kubernetes resources and their associated applications from connecting properly.
What Role Do Services Play in Making Containerized Applications Usable in Real-World Environments?
Services provide stable networking and access to applications running inside Pods, even when Pods are created, replaced, or scaled. Without Services, it would be much harder for users and other applications to reliably connect to workloads running in Kubernetes.
For Someone Already Using Docker, What Is the Next Logical Step to Start Working with Kubernetes Confidently?
The next step is to enable Kubernetes locally using Docker Desktop or a tool like minikube and start deploying the same containers they already know how to build. Learning how to create a Deployment and expose it with a Service is usually the best hands-on starting point. Fortunately, AI assistants like GitHub Copilot CLI, Claude Code, and others can help developers create, understand, and modify YAML used by Kubernetes.
How Can Attendees Learn More About This Topic, and Prepare for Your Session?
A great place to start is the official Kubernetes documentation at kubernetes.io along with hands-on experimentation using Docker Desktop. Coming in with a basic understanding of containers and Docker will help, but the session is designed to make Kubernetes approachable even for developers who are just getting started.
Note: Those wishing to attend the session can save money by registering early, according to the event's pricing page. "Save $400 by registering by the July 17 Super Early Bird Savings deadline!" said the organizer of the event, which is presented by the parent company of Visual Studio Magazine.
About the Author
David Ramel is an editor and writer at Converge 360.