Deploying k8s-v1.8.3 using rancherserver:v1.6.12

deploying k8s-v1.8.3 using rancherserver:v1.6.12

I. Brief description

Second, System Preparation

Three, run the command

Iv. Creating the Environment

Five, join the host

Vi. related Screenshots

Seven, reference links

I. Brief description

Rancher launched the rancher server:v1.6.11 on November 14, the biggest feature is the support of the latest k8sv1.8.3 version, and the Docker version of the support also added several versions, in addition to the commonly used Docker 1.12.6 stable version, Also beginning to support Docker 1.13.1 and Docker17.03.02 versions, users can have more choices.

However, the v1.6.11 version has been rancher as the latest version, rather than the stable version that can be used for production. Half a month after the trial run, rancher fixed some problems, officially launched rancher server:v1.6.12 version, and the version of the calibration as stable.

The original installation document is based on V1.6.11-RC3, there are some small errors (such as the command line in the-name and--name differences), now use the final v1.6.12 version, the installation k8s v1.8.3 the whole process again, this will help new friends fluent use of rancher.

Second, System preparation

Three machines are using Ubuntu 16.04.03 version, Docker 1.12.6. One as rancher Server, two as rancher Agent work node. For specific preparations, please see the reference link.

Rancher2 192.168.3.220 Server Management node

Node221 192.168.3.221 Agent Work node

Node222 192.168.3.222 Agent Work node

Three, run the command

#在Rancher2的Shell终端上, run the Docker command to start rancher Server

sudo docker run-d--restart always--name rancher-server-p 8080:8080 rancher/server:v1.6.12 && sudo docker logs -F Rancher-server

#待启动结束以后, through the http://192.168.3.220:8080 address, access to the rancher management end.

Iv. Creating the Environment

#1. Take the original kubernetes environment as a template, fine-tune the parameters, create a new template k8s-v1.8,

#2. Use this template to create an environment named Myk8s.

#进入Rancher的Web管理界面中,

#依次点击菜单中的 "Default"-"Environment Management"-"Add environment template".

#创建一个新的K8S环境, add the name "k8s-v1.8",

#选中 the "kubernetes" Orchestration Tool and click "Edit Settings" to adjust the parameters.

Private Registry for add-ons and Pod infra Container Images (Modify private warehouse address): registry.cn-shenzhen.aliyuncs.com

Image namespace for add-ons and Pod infra Container Images (Modify Aaons component namespace): RANCHER_CN

Image namespace for Kubernetes-helm (Modify Kubernetes-helm namespace): RANCHER_CN

Pod Infra Container Image (modify default pause mirror name): rancher_cn/pause-amd64:3.0

#2. Create an environment named Myk8s using the new template (k8s-v1.8).

Five, join the host

#在Rancher的Web界面中, select Add Host,

# "Host registration Address", "Current site address" is rancherserver IP address (http://192.168.3.220:8080)

#在第4步输入node221的主机IP地址,

#系统会自动生成主机加入到myK8S环境的Docker命令,

#通过Xshell终端以SSH方式, log in to the node221 node,

#将Web界面中的主机加入命令, paste to terminal, complete registration.

#到Web界面中查看主机注册的结果.

#稍等几分钟, and so rancher will k8s related mirrors downloaded and deployed,

#到myK8S环境中, review the k8s UI and check the final k8s deployment effect.

#再将node222主机节点加入到K8S环境中,

#稍等几分钟, wait patiently for the system to complete deployment.

Vi. Related Screenshots

01-Install Rancherserver-1.jpg

02-Install Rancherserver-2.jpg

03-default-Environment Management menu. jpg

04-Add environment template. jpg

05-Environment Template-kubernetes-edit settings. jpg

06-Template version is Kubernetes v1.8.3.jpg

07-Critical page-Modify k8s parameters. jpg

08-Critical page-Modify k8s Parameters-other parameters are not modified. jpg

09-Create k8s-v1.8 environment template. jpg

10-the environment template named k8s-v1.8 has been created. jpg

11-Create the MYK8S environment with the new k8s-v1.8 template. jpg

12-Create the MYK8S environment with the new k8s-v1.8 template. jpg

13-Infrastructure-add host-Host registration address. jpg

14-Add host-fill in Node221 IP address-automatically generate the host's registration command. jpg

15-on the Xshell terminal of node221, run the command to register the host. jpg

16-Wait a few minutes, the k8s has all been deployed and the components are in a normal state. jpg

17-Wait a few minutes, the k8s has all been deployed and the components are in a normal state. jpg

18-Wait a few minutes, the k8s has all been deployed and the components are in a normal state. jpg

19-Wait a few minutes, the k8s has all been deployed and the components are in a normal state. jpg

20-Wait a few minutes, the k8s has all been deployed and the components are in a normal state. jpg

21-Deployed K8s UI interface. jpg

22-Deployed K8s UI interface. jpg

23-Continue adding 2nd host node Node222.jpg

24-Continue adding 2nd host node Node222.jpg

25-Wait a moment-after adding the 2nd host node The node222 state has all been normal. jpg

26-Wait a moment-after adding the 2nd host node The node222 state has all been normal. jpg

27-Wait a moment-after adding the 2nd host node The node222 state has all been normal. jpg

28-2nd Node node222 after joining K8s ui.jpg

01-Install Rancherserver-1.jpg

02-Install Rancherserver-2.jpg

03-default-Environment Management menu. jpg

04-Add environment template. jpg

05-Environment Template-kubernetes-edit settings. jpg

06-Template version is Kubernetes v1.8.3.jpg

07-Critical page-Modify k8s parameters. jpg

08-Critical page-Modify k8s Parameters-other parameters are not modified. jpg

09-Create k8s-v1.8 environment template. jpg

10-the environment template named k8s-v1.8 has been created. jpg

11-Create the MYK8S environment with the new k8s-v1.8 template. jpg

12-Create the MYK8S environment with the new k8s-v1.8 template. jpg

13-Infrastructure-add host-Host registration address. jpg

14-Add host-fill in Node221 IP address-automatically generate the host's registration command. jpg

15-on the Xshell terminal of node221, run the command to register the host. jpg

16-Wait a few minutes, the k8s has all been deployed and the components are in a normal state. jpg

17-Wait a few minutes, the k8s has all been deployed and the components are in a normal state. jpg

18-Wait a few minutes, the k8s has all been deployed and the components are in a normal state. jpg

19-Wait a few minutes, the k8s has all been deployed and the components are in a normal state. jpg

20-Wait a few minutes, the k8s has all been deployed and the components are in a normal state. jpg

21-Deployed K8s