Basic Full reference: Http://blog.csdn.net/zhangjun2915/article/details/40598151kubernetes introduction
- Related information
- Https://github.com/GoogleCloudPlatform/kubernetes
- http://kubernetes.io/
- http://blog.csdn.net/zhangjun2915/article/details/40598151
- Overview:
- Google's open-source Docker-based mini PAAs system
- Capabilities cover resource scheduling, deployment operations, service discovery, capacity scaling
- General overview Map
- Manipulating objects
- Module components
- Functional characteristics
Basic Concept Pod
- Basic deployment unit that can be created, dispatched, managed, deleted, etc.
- Includes one or more Docker container for data sharing based on data volumes
- Centrally deployed to drive the same set of features
- Example: three components of a Web site (front end, back end, database) run in their own container, you can create pods with three container
Service
- The aggregation of pods (and pods are similar to instance and service concepts)
- Because the pod can change, or expand the scaling, the general interaction is based on service access
Replication Controllers
- Pod Life cycle Controller
- Responsible for the dynamic expansion and contraction of pod, to ensure the number of pods in line with the expected
Label
- Key/value Key-value pairs (based on ETCD)
- Tag tag for storing pods to correlate service and pod,replication controller and pod relationships
- Provides laber selector for external calls to get the value corresponding to the index
Cluster architecture
Masterapiserver
- As the entrance of kubernetes system, it encapsulates the operation of adding and deleting the core object.
- provided to external customers and internal component calls in a restful interface
- The rest objects it maintains are persisted to ETCD
Scheduler
- Responsible for the resource scheduling of the cluster, assigning the machine to the new pod
- As a component, it is easy to replace the other scheduler
Controller-manager
- Endpoint-controller
- Periodically correlate service and POD (association information maintained by endpoint objects)
- Ensure that service-to-pod mappings are always up-to-date.
- Replication-controller
- Periodically correlate Replicationcontroller and pods
- Ensure that the number of copies defined by the Replicationcontroller is always the same as the number of pods actually running
Slave (minion/host) Kubelet
- Responsible for the control of Docker containers, such as Start/stop, monitor operation status, etc.
- It periodically obtains pods assigned to the native from Etcd, and starts or stops the appropriate container based on pod information.
- Receive Apiserver HTTP requests to report the status of the pod.
Proxy
- Responsible for providing agent for pod
- Get all the service from ETCD regularly and create agents based on service information
- When a customer pod wants to access another pod, the access request is forwarded by the native proxy
Detailed process creation pod
Change Pod copy count information
Change Service Information
Kubernetes Getting Started learning notes
