The basic structure of Kubernetes Cluster

The basic structure of Kubernetes Cluster:

- Kubectl: It's a command-line tool that helps you to control - clusters.

- UI: The user interface of Kubernetes Dashboard.

- API: API is the end from where the user interacts with clusters.

- Scheduler: It's a process that assigns pods and nodes.

- API Server: It configures the data of API object Which includes

pods, nodes, replication controllers, services, etc.

- Control Manager: It watches the shared state of the cluster with the API server.

- ETCD: It is a distributed key-value store use to hold the critical information of the like configuration files.

- KubeProxy: It's a network-based proxy that is run on your every cluster. It maintains the rules of the network to the nodes.

- Kubelet: It is a node agent and runs on each node. It maintains a set of the pod which is provided through the various mechanisms.

- Container Runtime: Executes and maintains the container.

- Node: A node is a worker machine on Kubernetes it could be either a Physical or Virtual device as per the Cluster.

- Master: We have master in Kubernetes that work as a Manager and a Worker node as a Team member.

How cluster works: Worker node run containerized applications. The worker node runs the pod that is the component of the application. Each cluster has a worker node.Cluster managers the all.