Anyone who works in IT, in any capacity connected to software will have heard Kubernetes more than once.
While the answer is obvious to anyone in the prog/dev space and many people outside, for others it’s really unclear. People keep trying to explain it to me but it sounds like gibberish. please ?
In: 483
I think people are trying to encompass *everything* that Kubernetes is.
At the basic level, it’s a way to not have to manage your own machines. In the old days* you’d have a bunch of servers and you’d deploy your application to a couple of them.
If something went wrong anywhere in the running of the application (hardware failure, contention issues with other apps on the same server, bug in your code causing the program to crash) it was a manual effort between both sys admin and the app owners to ensure the app was brought back to a healthy state.
Unsurprisingly this doesn’t scale well on its own, so people built tools to manage problems that can occur and automate fixing them.
Kubernetes is one of the more successful attempts at this. The biggest change being that everything is kept in its own “container”, which is a nice little box around applications that make them as unlikely to break anything else on the server as possible. That means sys admins can focus on the infra problems and app owners can focus on the app problems.
* In the tech world, like 3-4 years ago
Latest Answers