How Pods access Kubernetes DNS in Docker EE, part two

This is part two of a two-part blog about internal DNS resolution and network access for Pods in Kubernetes. In part one we looked at how internal DNS services are configured in Kubernetes and how DNS resolution is configured for containers in Pods for user workloads. In this part, we will look at how network traffic gets from the containers in Pods for user workloads to the Pods providing DNS functionality.

How Pods access Kubernetes DNS in Docker EE, part one

Service discovery is one of the important benefits of using a container/Pod orchestrator. When you create a Service in Kubernetes, controllers running behind the scenes create an entry in the cluster’s DNS records so that other applications deployed in the cluster can look up the Service using its name. In part one of this blog, we will look at how DNS resolution is set up for containers in Pods.

What is Container Orchestration – Kubernetes Version?

In a previous post, What is Container Orchestration?, I explained container orchestration using some examples based on Docker Swarm. While Docker Swarm is undeniably easier to both use and explain, Kubernetes is by far the most prevalent container orchestrator today. So, I’m going to go through the same examples from that previous post but, this time, use Kubernetes. One of the great things about Docker Enterprise is it supports both Swarm and Kubernetes so I didn’t have to change my infrastructure at all.

What is Container Orchestration?

Over the last two or three years I’ve given a similar presentation on containers to operations groups at clients, potential clients, conferences and meetups. Generally, they’re just getting started with containers and are wondering what orchestration is and how it impacts them. In this post, I will talk about what container orchestration is and provide several videos with simple examples of what it means.