Kubernetes notes (5)--kubernetes layout

This is a creation in Article, where the information may have evolved or changed.

Node(also known minion as) runs docker container , and master is responsible for scheduling the management of these container .

MasterRun the following services:

1. API Server-nearly All the components on the master and nodes accomplish their respective tasks by making API calls. These is handled by the API Server running on the master.
2. ETCD-ETCD is a service whose job was to keep and replicate the current configuration and run state of the cluster. It is implemented as a lightweight distributed Key-value store and was developed inside the CoreOS project.
3. Scheduler and Controller Manager-these processes schedule Containers (actually, pods-but more on them later) onto Target N Odes. They also make sure, that the correct numbers of these things is running at all times.

NodeRun the following processes:

1. KUBELET-A Special Background process (daemon that runs on each node whose job are to respond to commands from the master to Create, destroy, and monitor the containers on that host.
2. Proxy-this is a simple network proxy, that's used to separate, the IP address of a target container from the name of the SER Vice it provides.
3. Cadvisor (optional)-http://bit.ly/1izygli[container Advisor (Cadvisor)] is a special daemon that collects, aggregates, PR Ocesses, and exports information about running containers. This information includes information about resource isolation, historical usage, and key network statistics.