Managing Docker containers with Kubernetes
Services and Replication
Kubernetes supports two other very interesting features that I have not mentioned so far. Using a replication controller, you can scale pods horizontally. On the basis of a pod label, you can tell Kubernetes to provide the pod x times. Kubernetes then generates the desired number of instances of the container and makes them available on the existing minions. Kubernetes also handles the task of keeping the number of instances up to date. For example, if you stipulated that you want to have four instances of your Apache pods, Kubernetes would automatically start or stop Apache Docker instances until the number of instances corresponds to the definition.
Even if the individual containers get IP addresses from a network block defined previously in Docker, access to the individual instances of a pod are more typically via services. To offer this access, Kubernetes drops a kind of abstraction layer over specific pods of the same type and assigns a single IP address to this service. Access to the individual instances of a pod is then via that service IP. To allow this to happen, the request to the service IP is forwarded to the individual minions, and the kubelet proxy service on the minions is responsible for forwarding the request to the correct container.
You can imagine such a service as a kind of load balancer for a specific set of pods (Figure 1). For this system to work, every minion host must have an additional network segment from which the pod is then assigned an IP address. The kubelet proxy services forward the request to exactly this IP address. However, the only cloud provider that offers such a network configuration out of the box is the Google cloud platform. For all other providers, even if you use the Atomic image from this article in a local virtualization environment, a manual Docker service configuration is required. See the Docker documentation [9].

The flannel
tool [10], which is included in the most recent releases of the Atomic image, makes it very easy to set up overlay networks, which Docker can then draw on, thus saving you from extensive manual configuration.
Conclusions
Even though Kubernetes is currently profoundly beta and the tool's emphasis on the Google cloud engine is obvious, the gains in flexibility compared with plain vanilla Docker installations are already huge. Kubernetes defines an additional abstraction layer for the existing hardware resources and makes them available as a large pool of hardware.
Which system ultimately runs the container is unimportant. Kubernetes independently pools the necessary resources and starts the container wherever resources are available. Through the use of replication controllers, the framework also helps to scale existing containers horizontally.
Kubernetes services help to facilitate access to a service through a single IP address, thus eliminating the cumbersome process of discovering container IP addresses. This feature is particularly valuable when you consider the fact that containers can be short lived; they are typically restarted just a short time later on a different host; thus, their IP address might change. Services abstract these changes, removing the need for configurations such as upstream load balancers.
Infos
- Google Kubernetes: https://github.com/kubernetes/kubernetes
- Project Atomic: http://www.projectatomic.io/
- Red Hat Enterprise Linux 7 Atomic host: http://www.redhat.com/en/about/blog/small-footprint-big-impact-red-hat-enterprise-linux-7-atomic-host-beta-now-available
- Fedora Atomic host: https://getfedora.org/en/cloud/download/
- CentOS 7 Atomic host: http://buildlogs.centos.org/rolling/7/
- Etcd API documentation: https://github.com/coreos/etcd/blob/master/Documentation/api.md/
- Setup instructions for an Atomic VM https://access.redhat.com/articles/rhel-atomic-documentation/
- Cloud-init documentation: https://cloudinit.readthedocs.org/en/latest/
- Docker network documentation: http://docs.docker.com/engine/userguide/networking/
- Flannel overlay network: https://github.com/coreos/flannel/
« Previous 1 2
Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.

News
-
First Release Candidate for Linux Kernel 6.14 Now Available
Linus Torvalds has officially released the first release candidate for kernel 6.14 and it includes over 500,000 lines of modified code, making for a small release.
-
System76 Refreshes Meerkat Mini PC
If you're looking for a small form factor PC powered by Linux, System76 has exactly what you need in the Meerkat mini PC.
-
Gnome 48 Alpha Ready for Testing
The latest Gnome desktop alpha is now available with plenty of new features and improvements.
-
Wine 10 Includes Plenty to Excite Users
With its latest release, Wine has the usual crop of bug fixes and improvements, along with some exciting new features.
-
Linux Kernel 6.13 Offers Improvements for AMD/Apple Users
The latest Linux kernel is now available, and it includes plenty of improvements, especially for those who use AMD or Apple-based systems.
-
Gnome 48 Debuts New Audio Player
To date, the audio player found within the Gnome desktop has been meh at best, but with the upcoming release that all changes.
-
Plasma 6.3 Ready for Public Beta Testing
Plasma 6.3 will ship with KDE Gear 24.12.1 and KDE Frameworks 6.10, along with some new and exciting features.
-
Budgie 10.10 Scheduled for Q1 2025 with a Surprising Desktop Update
If Budgie is your desktop environment of choice, 2025 is going to be a great year for you.
-
Firefox 134 Offers Improvements for Linux Version
Fans of Linux and Firefox rejoice, as there's a new version available that includes some handy updates.
-
Serpent OS Arrives with a New Alpha Release
After months of silence, Ikey Doherty has released a new alpha for his Serpent OS.