{"id":10190,"date":"2020-03-01T17:06:08","date_gmt":"2020-03-01T16:06:08","guid":{"rendered":"https:\/\/blog.mi.hdm-stuttgart.de\/?p=10190"},"modified":"2023-06-18T18:18:06","modified_gmt":"2023-06-18T16:18:06","slug":"autoscaling-of-docker-containers-in-google-kubernetes-engine","status":"publish","type":"post","link":"https:\/\/blog.mi.hdm-stuttgart.de\/index.php\/2020\/03\/01\/autoscaling-of-docker-containers-in-google-kubernetes-engine\/","title":{"rendered":"Autoscaling of Docker Containers in Google Kubernetes Engine"},"content":{"rendered":"\n
\n

The name Kubernetes comes originally from the Greek word for helmsman. It is the person who steers a ship or boat. Representing a steering wheel, the Kubernetes logo was most likely inspired by it. [1<\/a>] <\/p>\n\n\n\n

The choice of the name can also be interpreted to mean that Kubernetes (the helmsman) steers a ship that contains several containers (e.g. docker containers). It is therefore responsible for bringing these containers safely to their destination (to ensure that the journey goes smoothly) and for orchestrating them.<\/p>\n\n\n\n

Apparently Kubernetes was called Seven of Nine<\/em> within Google. The Star Trek fans under us should be familiar with this reference. Having 7 spikes, there might be a connection between the logo and this name. [2<\/a>]<\/p>\n\n\n\n

This blog post was created during the master lecture System Engineering and Management<\/em>. In this lecture we deal with topics that are of interest to us and with which we would like to conduct experiments. We have already worked with docker containers very often and appreciate the advantages. Of course we have also worked with several containers within a closed system orchestrated by Docker-Compose configurations. Nevertheless, especially in connection with scaling and the big companies like Netflix or Amazon, you hear the buzzword Kubernetes and quickly find out that a distribution of a system to several nodes requires a platform such as Kubernetes.<\/p>\n\n\n\n\n\n\n\n

Who is this blog post for? <\/strong><\/h3>\n\n\n\n

If you know what Docker Containers are and how they are built and used, the next step may be to create multiple instances of them and distribute the load. Of course this is possible with a Docker-Compose configuration, but the containers will only run on one computer at a time. So as soon as the computer reaches its physical limits, it is absolutely necessary to distribute the services and the instances thereof to several nodes. This is exactly what Kubernetes is suitable for, as it is used to orchestrate containers in a distributed system. In this blog post we will start exactly at this point and assume that you have basic experience with Docker and Kubernetes. The focus is on scaling containers within a Kubernetes cluster.<\/p>\n\n\n\n

Of course all others who found their way to this blog post are also invited to read the blog post in order to learn more about Kubernetes, the autoscaling of services in docker containers plus the visualization of their utilization.<\/p>\n\n\n\n

We will share and discuss our experiences about what we have built, what we have learned and difficulties we have encountered during our experiments. <\/p>\n\n\n\n

What is our goal?<\/strong><\/h3>\n\n\n\n

First of all we just wanted to start with Kubernetes, experiment and build something with as little effort as possible and see results. But even the first question can be a challenge. Where to start? <\/p>\n\n\n\n