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
**Containers:**
Its best practice to deploy software in **Containers**. You can think of it like a seperate OS, which is running only to run this one programm on there (like a server). We do this to avoid side effects from junk or other stuff that could be interfering with that one programm you want to deploy. If you want to read more about this here are the 2 most popular used tools for this: [Docker](https://www.docker.com/) and [Podman](https://podman.io/)
**Kubernetes:**
For some big Websites (for example) its best to deploy more containers based on how many users currently want to use the side. Here is where [**Kubernetes**](https://kubernetes.io/) comes to play to spin up as many containers as needed.
We call that **Loadbalancing** (or **scaling**) however this is only one usecase for Kubernetes (probably the most important one tho).
Other use cases are management of these containers in general (**scheduling)** like updating, restarting (**making sure the programm doesnt fail**), and their communication in general (like networking, storage)
**Why its important:**
Kubernetes is a code like configuration tool for infrastruktur which you can run on your own server, in the cloud, or in hybrid environments which is pretty cool but a pain in the ass to setup tho. Using it can **safe** your company **a lot of money** (**by scaling correctly** for example, or avoiding crashes etc..), however not every project should use Kubernetes but a lot of teams default to it because its “the thing to do” as only large scale projects really benefit from using it.
Latest Answers