Hello All,

Today’s topic is what Kubernetes do and don’t? Let me add the high-level concepts so that it will help to know what K8S does and don’t

Do:

• Kubernetes uses for Service discovery and load balancing.
• In K8s you can add the storage as you like no matter its local storage or public cloud storage and it can do your storage orchestration very smoothly for you.
• K8s support automatic bin packing. You can define the limit of the CPU and RAM that are required for each container of your deployment and Kubernetes place your pod as per the configuration to a specific node.
• K8s also support the automated Rollouts and rollbacks by checking the desired state defined in the deployment configuration.
• Self-healing is the beauty of the Kubernetes where it restarts containers that failed and also replaces the containers or may kill the containers if it does not respond to the health checkup.
• Kubernetes can help you to deploy and update the application configuration without rebuilding the container image, as it has good secrete and configuration management support.

don’t:

• Kubernetes do not limit the type of application supported, which means you can run the stateful and stateless application as well as the data processing workloads to the Kubernetes as long as if application run perfectly in containers that will run on the Kubernetes too.
• kubernetes does not deploy source code and does not build your application.
• it also does not provide application-level services. which means not storage, middleware, or databases but you can run those services on the Kubernetes.
• K8s does not provide nor mandate a configuration language as it provides the declarative API that may be targeted arbitrary form of the declarative specifications.

These are a few important do and don’t of the Kubernetes that help to define the Kubernetes.