DevOps

Day 6-Kubernetes Architecture

ZT AdminBy No Comments5 Mins Read

Introduction: Learning Objectives

In this section, we will be able to:

  1. Identify the components of a Kubernetes architecture,
  2. identify the components of a control plane,
  3. and identify the components of a worker plane.

Kubernetes Architecture

This architecture diagram highlights the main components in a Kubernetes system.

 

Kubernetes Control Plane

  1. A deployment of Kubernetes is called a Kubernetes cluster.
  2. A Kubernetes cluster is a cluster of nodes that runs containerized applications.
  3. Each cluster has one master node (the Kubernetes Control Plane) and one or more worker nodes.
  4. The control plane maintains the intended cluster state by making decisions about the cluster and detecting and responding to events in the cluster.
  5. As an analogy, it is similar to a thermostat. You specify the desired temperature, and the thermostat regulates heating and cooling systems continuously to achieve the specified state.
  6. An example of a decision made by the control plane is the scheduling of workloads, and an example of responding to an event is creating new resources when an application is deployed.

Kubernetes Worker Nodes

  1. Nodes are the worker machines in a Kubernetes cluster. In other words, user applications are run on nodes.
  2. Nodes are not created by Kubernetes itself, but rather by the cloud provider. This allows Kubernetes to run on a variety of infrastructures.
  3. The nodes are then managed by the control plane.

Kubernetes API Server

  1. In the Kubernetes control plane, the Kubernetes API server exposes the Kubernetes API.
  2. The API server serves as the front-end for the control plane.
  3. All communication in the cluster utilizes this API. For example, the Kubernetes API server accepts commands to view or change the state of  the cluster.
  4. The main implementation of a Kubernetes API server is kube-apiserver which is designed to scale horizontally—by deploying more instances.
  5. You can run several instances of kube-apiserver and balance traffic between those instances.

Etcd

  1. Etcd is a highly available, distributed key value store that contains all the cluster data.
  2. When you tell Kubernetes to deploy your application, that deployment configuration is stored in etcd.
  3. Etcd defines the state in a Kubernetes cluster, and the system works to bring the actual state to match the desired state.

Scheduler

  1. The Kubernetes scheduler assigns newly created Pods to nodes.
  2. This basically means that the kube-scheduler determines where your workloads should run within the cluster.
  3. The scheduler selects the most optimal node according to Kubernetes scheduling principles, configuration options, and available resources.

Kubernetes Controller Manager