Architecture Building Block: Kubernetes Container Management
If you are thinking about adding Kubernetes to your architecture it’s nice to have a starting point that shows what all is included and how they fit together.
You’re basically looking at two node types - master and worker - with network interactions between an API and runtime service.
Master Node
Okay, arguably the terminology is falling out of favor, and should be. The master, or management node is responsible for services that are required to orchestrate the activity across all nodes.
Master Service
This service contains the schedule and controller manager, and serves up an API interface for interacting with the worker nodes.
etcd Service
Configuration management is provided by an etcd service.
Worker Node
The worker node operates two services. This node scales out according to the requireed number of containers and their required resources.
Workload Service
The workload service contains a user pod component that runs the actual Docker containers.
Kubelet Service
The Kubelet Service is the agent working on behalf of the management node to ensure that the specified number of containers are running and healthy.
Here is a list of features provided by Kubernetes. If you run minikube there are commands and flags to become familiar with.