Shulou(Shulou.com)06/02 Report--

Main points of content:

1. Experimental environment

II. Single master cluster deployment

III. Multi-master cluster deployment

First, the experimental environment:

Based on the previous blog: the environment deployed by https://blog.51cto.com/14475876/2470049

II. Single master cluster deployment

Single master cluster architecture diagram:

The following is a list of self-signed SSL certificates:

1. First of all, we need to understand that we need to deploy the following three core components on Master:

Kube-apiserver: it is the unified entrance to the cluster, and the coordinator of each component. All object resource additions, deletions, modifications, and monitoring operations are handed over to APIServer and then submitted to Etcd for storage.

Kube-controller-manager: handles regular background tasks in the cluster, with each resource corresponding to a controller, and controller-manager is responsible for managing these controllers

Kube-scheduler: select a Node node for the newly created Pod according to the scheduling algorithm, which can be deployed arbitrarily, on the same node or on different nodes.

Operation procedure: configuration File-> systemd Management components-> start

-- deployment begins:

Next is the operation on master to generate the api-server certificate:

Upload the downloaded master.zip package on the host to the / root/k8s/ directory, and extract: [root@localhost K8s] # unzip master.zip [root@localhost K8s] # mkdir / opt/kubernetes/ {cfg,bin,ssl}-p [root@localhost K8s] # mkdir k8s-cert/ / directory to create the apiserver self-signed certificate [root@localhost K8s] # cd k8s-cert/ [root@localhost k8s-cert] # vim k8s-cert.shcat > ca-config.json

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.