Kubernetes was designed, originally by Google. Now, it is maintained by the Cloud Native Computing Foundation (Linux).

It works with container tools* (including Docker Swarm).

According to the official website, Kubernetes is “an open-source system for automating deployment, scaling, and management of containerized applications”.

Whoa, whoa, whoa… Wait!!!

Now, if this definition raised your eyebrows, or made you roll your eyes in confusion…
I welcome you to this article…

Before analysing the definition, let’s first know what does a container mean in context to here…
Container: It is an executable piece of package from a program, which can not run on it’s own. Thus, needing tools to run anywhere.

Vice versa, they can be used by a software to run anywhere, especially when moved from one computer environment to another.

For example, if we have built a small software using IDE X(version 2.4) and wish to run the software in IDE X(version 3.5), mst of the code won’t give the expected results.
Thus, the built-in libraries of container would help the program to run anywhere.

Now, let’s go back to the definition-

Open source: Kubernetes is an open-source system, which means it is not governed by anyone (nor by Google, nor by Linux, completely). It can be used by anyone free of cost, and can be modified,as per the requirements in future, by anyone.
Automation of deployment: Maps the Stakeholders and steps involved in joining(clustering) of containers together.
Scaling and managing containers (applications): Kubernetes manages the containers used to run a program.

Last words

Kubernetes provides a working environment for large programs to run, scales it’s flexibility and working, and caters to it’s needs on it’s own.
So, basically, Kubernetes is a guide to your real-time application to survive everywhere.