# Why (And When) You Should Use Kubernetes | Hacker Noon ![rw-book-cover](https://readwise-assets.s3.amazonaws.com/static/images/article3.5c705a01b476.png) URL:: https://hackernoon.com/why-and-when-you-should-use-kubernetes-8b50915d97d8 Author:: Originally Published ## Highlights > It’s not enough to run containers; you need to be able to: > Integrate and orchestrate these modular parts > Scale up and scale down based on the demand > Make them fault tolerant > Provide communication across a cluster ([View Highlight](https://instapaper.com/read/1391000008/15644592)) > tools are today known as container schedulers. ([View Highlight](https://instapaper.com/read/1391000008/15644593)) > Kubernetes has some great features that allow you to deploy applications faster with scalability in mind: > Horizontal infrastructure scaling: New servers can be added or removed easily. > Auto-scaling: Automatically change the number of running containers, based on CPU utilization or other application-provided metrics. > Manual scaling: Manually scale the number of running containers through a command or the interface. > Replication controller: The replication controller makes sure your cluster has an equal amount of pods running. If there are too many pods, the replication controller terminates the extra pods. If there are too few, it starts more pods. > Health checks and self-healing: Kubernetes can check the health of nodes and containers ensuring your application doesn’t run into any failures. Kubernetes also offers self-healing and auto-replacement so you don’t need to worry about if a container or pod fails. > Traffic routing and load balancing: Traffic routing sends requests to the appropriate containers. Kubernetes also comes with built-in load balancers so you can balance resources in order to respond to outages or periods of high traffic. > Automated rollouts and rollbacks: Kubernetes handles rollouts for new versions or updates without downtime while monitoring the containers’ health. In case the rollout doesn’t go well, it automatically rolls back. > Canary Deployments: Canary deployments enable you to test the new deployment in production in parallel with the previous version. ([View Highlight](https://instapaper.com/read/1391000008/15644604)) --- Title: Why (And When) You Should Use Kubernetes | Hacker Noon Author: Originally Published Tags: readwise, articles date: 2024-01-30 --- # Why (And When) You Should Use Kubernetes | Hacker Noon ![rw-book-cover](https://readwise-assets.s3.amazonaws.com/static/images/article3.5c705a01b476.png) URL:: https://hackernoon.com/why-and-when-you-should-use-kubernetes-8b50915d97d8 Author:: Originally Published ## AI-Generated Summary None ## Highlights > It’s not enough to run containers; you need to be able to: > Integrate and orchestrate these modular parts > Scale up and scale down based on the demand > Make them fault tolerant > Provide communication across a cluster ([View Highlight](https://instapaper.com/read/1391000008/15644592)) > tools are today known as container schedulers. ([View Highlight](https://instapaper.com/read/1391000008/15644593)) > Kubernetes has some great features that allow you to deploy applications faster with scalability in mind: > Horizontal infrastructure scaling: New servers can be added or removed easily. > Auto-scaling: Automatically change the number of running containers, based on CPU utilization or other application-provided metrics. > Manual scaling: Manually scale the number of running containers through a command or the interface. > Replication controller: The replication controller makes sure your cluster has an equal amount of pods running. If there are too many pods, the replication controller terminates the extra pods. If there are too few, it starts more pods. > Health checks and self-healing: Kubernetes can check the health of nodes and containers ensuring your application doesn’t run into any failures. Kubernetes also offers self-healing and auto-replacement so you don’t need to worry about if a container or pod fails. > Traffic routing and load balancing: Traffic routing sends requests to the appropriate containers. Kubernetes also comes with built-in load balancers so you can balance resources in order to respond to outages or periods of high traffic. > Automated rollouts and rollbacks: Kubernetes handles rollouts for new versions or updates without downtime while monitoring the containers’ health. In case the rollout doesn’t go well, it automatically rolls back. > Canary Deployments: Canary deployments enable you to test the new deployment in production in parallel with the previous version. ([View Highlight](https://instapaper.com/read/1391000008/15644604))