The Kubernetes master is what the DevOps team interact with and use for provisioning new nodes, deploying new apps and resource monitoring and management. Now, of course, the master node itself can fail and take the whole cluster with it, so Kubernetes actually allows you to have multiple master nodes for redundancy’s sake.Ī bird’s eye view of a typical Kubernetes deployment Kubernetes Master
The master is responsible for scheduling tasks, managing workloads and securely adding new nodes to the cluster.
Like any distributed system, a Kubernetes cluster has a master node and then a whole lot of worker nodes which is where your applications would actually run. Scaling out here involves adding more compute nodes to give your growing application more leg room to operate. Second is scalability, where you want to scale ‘out’. You want your e-commerce website to stay online 24/7, or you will lose business, use Kubernetes for that. Now, why would you need to have a distributed environment in the first place?įor multiple reasons, first and foremost is high availability. The idea is to have a distributed system for containerized applications to run on. It takes the idea of containers and extends it to work across multiple compute nodes (which could be cloud hosted virtual machine or bare metal servers). Kubernetes comes into picture to solve these problems. For example, if the data center, where your servers are running, is under maintenance your application will go offline. That is great! However, it doesn’t provide immunity from system failures, network failure or disk failures. The apps are now bundled with the dependencies that they need, in a lightweight container instead of a VM. Not in the sense that you don’t need a production system at all, but you don’t have to worry about the specificity of the production environment.
#What is kubernetes used for software
What is Kubernetes? And what is its architecture?Ĭontainerization has cut the cord between software developers and the production environment.
0 kommentar(er)
