Anyone who has ever encountered K8S containers knows that the larger the number of them, the more administrative burden they have to endure. In the meantime, questions such as:
The services of the Kubernetes platform are able to solve all the above mentioned problems. The management, scaling and deployment of K8S containers can also be automated.
Rolling upgrade and rolling downgrade can be implemented, which means that we can update a container to a new version without stopping. In case of an error, we can revert to an older version.
If one of our virtual servers stops, Kubernetes can notice the error and place our application on an available server. With its help, we can maintain several replicas of the same application on several servers at the same time, so we don’t even have to count on minimal downtime.
When we perform planned maintenance, we can move our containers from the server we want to maintain to a temporary server with great security and without downtime.
When our applications get a bigger load and need to temporarily serve more clients, Kubernetes can scale our containers horizontally and evenly distribute the load on the available servers.
I managed to start my first cluster, but… when running your own Kubernetes cluster, several embarrassing questions may arise: