What is container orchestration and Kubernetes

We know that we can pack this application as the images with all its libraries and dependencies and run them as containers. So running a few containers is fine, but when you see a production-ready scenario where you want to run thousands of containers, you need container orchestration because you cannot create, manage, and do many things manually.

Container orchestration system is a concept that has some of its features with a container orchestrator by which it should be able to create and manage thousands of containers. It should be able to monitor those containers and their state, and it should scale based on the workloads. It should also handle all the container networking, and it should be able to self-heal the containers if one goes down or it goes out of memory, or anything happens to the containers. These are some of the characteristics of container orchestration because these are the essential characteristics.

Now let's dive into Kubernetes. So Kubernetes, aka k8s, the 8 is just a number of alphabets between K and S. It is a container orchestrator. By definition, Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications. So Kubernetes was born at Google, and it shares the same DNA as BORG and OMEGA. So BORG and OMEGA were other systems and solutions developed at Google in the past decades. From that experience and community support, Kubernetes has become one of the de facto standards for running containers in a production-ready environment. It's a CNCF Graduated Project.