rancher導入rke

原創 尚浩宇 2018-12-05 21:10

一、搭建RKE集羣

1.1 概述

    REK是Rancher Kubernetes Engine，通過rke工具可以快速簡單地搭建一套 Kubernetes集羣。

    搭建的重點在於環境，如果環境配置正確，一切都會很順利。

1.2 環境準備

    首先說明下依賴版本：    

序號 名稱 版本 備註
1 ubuntu 16.04.1  
2 docker 17.03.2-ce  
3 rke 0.1.1  
4 k8s 1.8.7  
5 rancher 2.0.0-alpha16  

    然後開始準備環境，注意需要兩臺機器，一臺用於安裝rke集羣，一臺用於rke工具控制機。注意控制機最好和rke集羣執行同樣的環境準備，否則有可能出現莫名安裝不上的問題。

    1、初裝的ubuntu自帶的編輯命令不太好用，這裏卸載原來的，然後安裝vi

#此時未使用root登陸，需要增加sudo，以獲取root權限
#首先卸載舊版本的vi編輯器：
sudo apt-get remove vim-common
#然後安裝新版vi即可：
$sudo apt-get install vim

    2、ubuntu默認不允許使用root登陸，爲了減少不必要的麻煩，這裏修改配置啓用root，然後以後所有步驟都在root用戶下操作。

#1、將PermitRootLogin prohibit-password修改爲PermitRootLogin yes
#2、取消註釋AuthorizedKeysFile      %h/.ssh/authorized_keys
sudo vi /etc/ssh/sshd_config 
#3、切換到root登陸
sudo su
#4、設置root密碼
sudo passwd root
#5、更新密碼
sudo passwd -u root
#6、重啓ssh
sudo service ssh restart

    修改完後，使用root登陸，重新打開客戶端。

    3、修改主機名，注意不能包含大寫字母，並且最好不要包含特殊字符,修改完後重啓機器。

vi /etc/hostname

    4、確保hosts文件包含如下行

127.0.0.1      localhost

    另外ubuntu會把主機名對應127.0.0.1加入到hosts裏，第三步我們改了名稱，所以hosts也要相應改變，但注意IP要改爲真實IP

172.16.10.99       worker02

    5、啓用cgroup內存和Swap限額，修改/etc/default/grub 配置文件，修改/增加兩項

GRUB_CMDLINE_LINUX_DEFAULT="cgroup_enable=memory swapaccount=1"
GRUB_CMDLINE_LINUX="cgroup_enable=memory swapaccount=1"

    修改完後執行

update-grub

    執行完後，再次重啓機器。

    6、永久禁用交換分區，直接修改/etc/fstab文件，註釋掉swap項

# swap was on /dev/sda6 during installation
#UUID=5e4b0d14-ad10-4d24-8f7c-4a07c4eb4d29 none            swap    sw              0       0

    7、其他的檢查防火牆（默認無規則）、SELinux（默認未啓用）、ipv4轉發（默認已啓用）、配置rke控制機到rke集羣機器的單向免密登陸

    8、下載安裝docker17.03.2-ce版本（https://docs.docker.com/install/linux/docker-ce/ubuntu/#upgrade-docker-ce），最好再設置加速器，不然下載鏡像會很慢。最後將root再添加到docker用戶組中。

1.3安裝rke

    rke的github地址是https://github.com/rancher/rke，點擊到releases頁面，下載rke工具。下載成功後，無需其他操作，只需要賦權即可使用。

chmod 777 rke
#驗證安裝
./rke -version

 1.4部署rke集羣

    1、重啓一下機器（爲什麼重啓？不知道，偶發裝不上，重啓就好了，這裏爲了確保成功，先重啓下。）

    2、創建cluster.yml文件，內容類似如下：

nodes:
  - address: 172.16.10.99
    user: root
    role: [controlplane,worker,etcd]
services:
  etcd:
    image: quay.io/coreos/etcd:latest
  kube-api:
    image: rancher/k8s:v1.8.3-rancher2
  kube-controller:
    image: rancher/k8s:v1.8.3-rancher2
  scheduler:
    image: rancher/k8s:v1.8.3-rancher2
  kubelet:
    image: rancher/k8s:v1.8.3-rancher2
  kubeproxy:
    image: rancher/k8s:v1.8.3-rancher2

    注意etcd的那個鏡像，不要更換其他etcd鏡像，更換會導致啓動403錯誤。quay.io的鏡像比較慢，可以先pull下來，但絕對不能換。

    3、執行

./rke  up --config cluster.yml

執行結果如下：

root@master:/opt/rke# ./rke up --config cluster-99.yml
INFO[0000] Building Kubernetes cluster                  
INFO[0000] [dialer] Setup tunnel for host [172.16.10.99] 
INFO[0000] [network] Deploying port listener containers 
INFO[0001] [network] Successfully started [rke-etcd-port-listener] container on host [172.16.10.99] 
INFO[0001] [network] Successfully started [rke-cp-port-listener] container on host [172.16.10.99] 
INFO[0002] [network] Successfully started [rke-worker-port-listener] container on host [172.16.10.99] 
INFO[0002] [network] Port listener containers deployed successfully 
INFO[0002] [network] Running all -> etcd port checks    
INFO[0003] [network] Successfully started [rke-port-checker] container on host [172.16.10.99] 
INFO[0004] [network] Successfully started [rke-port-checker] container on host [172.16.10.99] 
INFO[0004] [network] Running control plane -> etcd port checks 
INFO[0005] [network] Successfully started [rke-port-checker] container on host [172.16.10.99] 
INFO[0005] [network] Running workers -> control plane port checks 
INFO[0005] [network] Successfully started [rke-port-checker] container on host [172.16.10.99] 
INFO[0006] [network] Checking KubeAPI port Control Plane hosts 
INFO[0006] [network] Removing port listener containers  
INFO[0006] [remove/rke-etcd-port-listener] Successfully removed container on host [172.16.10.99] 
INFO[0007] [remove/rke-cp-port-listener] Successfully removed container on host [172.16.10.99] 
INFO[0007] [remove/rke-worker-port-listener] Successfully removed container on host [172.16.10.99] 
INFO[0007] [network] Port listener containers removed successfully 
INFO[0007] [certificates] Attempting to recover certificates from backup on host [172.16.10.99] 
INFO[0007] [certificates] No Certificate backup found on host [172.16.10.99] 
INFO[0007] [certificates] Generating kubernetes certificates 
INFO[0007] [certificates] Generating CA kubernetes certificates 
INFO[0008] [certificates] Generating Kubernetes API server certificates 
INFO[0008] [certificates] Generating Kube Controller certificates 
INFO[0009] [certificates] Generating Kube Scheduler certificates 
INFO[0011] [certificates] Generating Kube Proxy certificates 
INFO[0011] [certificates] Generating Node certificate   
INFO[0012] [certificates] Generating admin certificates and kubeconfig 
INFO[0012] [certificates] Generating etcd-172.16.10.99 certificate and key 
INFO[0013] [certificates] Temporarily saving certs to etcd host [172.16.10.99] 
INFO[0018] [certificates] Saved certs to etcd host [172.16.10.99] 
INFO[0018] [reconcile] Reconciling cluster state        
INFO[0018] [reconcile] This is newly generated cluster  
INFO[0018] [certificates] Deploying kubernetes certificates to Cluster nodes 
INFO[0024] Successfully Deployed local admin kubeconfig at [./kube_config_cluster-99.yml] 
INFO[0024] [certificates] Successfully deployed kubernetes certificates to Cluster nodes 
INFO[0024] Pre-pulling kubernetes images                
INFO[0024] Kubernetes images pulled successfully        
INFO[0024] [etcd] Building up Etcd Plane..              
INFO[0025] [etcd] Successfully started [etcd] container on host [172.16.10.99] 
INFO[0025] [etcd] Successfully started Etcd Plane..     
INFO[0025] [controlplane] Building up Controller Plane.. 
INFO[0026] [controlplane] Successfully started [kube-api] container on host [172.16.10.99] 
INFO[0026] [healthcheck] Start Healthcheck on service [kube-api] on host [172.16.10.99] 
INFO[0036] [healthcheck] service [kube-api] on host [172.16.10.99] is healthy 
INFO[0037] [controlplane] Successfully started [kube-controller] container on host [172.16.10.99] 
INFO[0037] [healthcheck] Start Healthcheck on service [kube-controller] on host [172.16.10.99] 
INFO[0037] [healthcheck] service [kube-controller] on host [172.16.10.99] is healthy 
INFO[0038] [controlplane] Successfully started [scheduler] container on host [172.16.10.99] 
INFO[0038] [healthcheck] Start Healthcheck on service [scheduler] on host [172.16.10.99] 
INFO[0038] [healthcheck] service [scheduler] on host [172.16.10.99] is healthy 
INFO[0038] [controlplane] Successfully started Controller Plane.. 
INFO[0038] [authz] Creating rke-job-deployer ServiceAccount 
INFO[0038] [authz] rke-job-deployer ServiceAccount created successfully 
INFO[0038] [authz] Creating system:node ClusterRoleBinding 
INFO[0038] [authz] system:node ClusterRoleBinding created successfully 
INFO[0038] [certificates] Save kubernetes certificates as secrets 
INFO[0039] [certificates] Successfully saved certificates as kubernetes secret [k8s-certs] 
INFO[0039] [state] Saving cluster state to Kubernetes   
INFO[0039] [state] Successfully Saved cluster state to Kubernetes ConfigMap: cluster-state 
INFO[0039] [worker] Building up Worker Plane..          
INFO[0039] [sidekick] Sidekick container already created on host [172.16.10.99] 
INFO[0040] [worker] Successfully started [kubelet] container on host [172.16.10.99] 
INFO[0040] [healthcheck] Start Healthcheck on service [kubelet] on host [172.16.10.99] 
INFO[0046] [healthcheck] service [kubelet] on host [172.16.10.99] is healthy 
INFO[0046] [worker] Successfully started [kube-proxy] container on host [172.16.10.99] 
INFO[0046] [healthcheck] Start Healthcheck on service [kube-proxy] on host [172.16.10.99] 
INFO[0052] [healthcheck] service [kube-proxy] on host [172.16.10.99] is healthy 
INFO[0052] [sidekick] Sidekick container already created on host [172.16.10.99] 
INFO[0052] [healthcheck] Start Healthcheck on service [kubelet] on host [172.16.10.99] 
INFO[0052] [healthcheck] service [kubelet] on host [172.16.10.99] is healthy 
INFO[0052] [healthcheck] Start Healthcheck on service [kube-proxy] on host [172.16.10.99] 
INFO[0052] [healthcheck] service [kube-proxy] on host [172.16.10.99] is healthy 
INFO[0052] [sidekick] Sidekick container already created on host [172.16.10.99] 
INFO[0052] [healthcheck] Start Healthcheck on service [kubelet] on host [172.16.10.99] 
INFO[0052] [healthcheck] service [kubelet] on host [172.16.10.99] is healthy 
INFO[0052] [healthcheck] Start Healthcheck on service [kube-proxy] on host [172.16.10.99] 
INFO[0052] [healthcheck] service [kube-proxy] on host [172.16.10.99] is healthy 
INFO[0052] [worker] Successfully started Worker Plane.. 
INFO[0052] [network] Setting up network plugin: flannel 
INFO[0052] [addons] Saving addon ConfigMap to Kubernetes 
INFO[0053] [addons] Successfully Saved addon to Kubernetes ConfigMap: rke-network-plugin 
INFO[0053] [addons] Executing deploy job..              
INFO[0058] [sync] Syncing nodes Labels and Taints       
INFO[0058] [sync] Successfully synced nodes Labels and Taints 
INFO[0058] [addons] Setting up KubeDNS                  
INFO[0058] [addons] Saving addon ConfigMap to Kubernetes 
INFO[0058] [addons] Successfully Saved addon to Kubernetes ConfigMap: rke-kubedns-addon 
INFO[0058] [addons] Executing deploy job..              
INFO[0063] [addons] KubeDNS deployed successfully..     
INFO[0063] [ingress] Setting up nginx ingress controller 
INFO[0063] [addons] Saving addon ConfigMap to Kubernetes 
INFO[0063] [addons] Successfully Saved addon to Kubernetes ConfigMap: rke-ingress-controller 
INFO[0063] [addons] Executing deploy job..              
INFO[0068] [ingress] ingress controller nginx is successfully deployed 
INFO[0068] [addons] Setting up user addons..            
INFO[0068] [addons] No user addons configured..         
INFO[0068] Finished building Kubernetes cluster successfully

    如果執行過程出現錯誤，可以先執行remove，再執行up，如果還不行，先remove再重啓機器，最後在up。一般都會成功，如果執行了如上步驟還不行，再看具體報錯信息。

二、導入rke到rancher2.0（預覽版）

    點擊創建集羣，在最右邊有個導入現有集羣。

    執行rke命令的目錄下會自動生成一個kube_config_cluster.yml文件，點擊頁面的導入，把該文件導入。

    注意：rancher2.0，現在都是開發版，存在各種問題，僅適合調研用，缺少很多東西，不適合生產用。消息說三月底會推送2.0正式版。

三、附錄

    rke安裝注意事項：http://blog.csdn.net/csdn_duomaomao/article/details/79325759

    rancher導入rke：http://blog.csdn.net/csdn_duomaomao/article/details/79325436

發表評論
所有評論
還沒有人評論，想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章

linux上安裝Docker(非常簡單的安裝方法)

幸運券發放 2019-02-24 19:38:01

Error response from daemon: OCI runtime create failed

uiz 2019-02-24 13:44:10

『高級篇』docker之kubernetes基礎集羣附加功能kube-proxy和kube-dns（

IT人故事 2019-02-23 14:07:34

寶塔面板 + Rancher + 阿里雲鏡像倉庫 + Docker + Kubernetes，添加集羣、部署 web 應用

燕小范 2019-02-23 13:20:14

jenkins觸發式自動構建docker鏡像上傳至harbor併發布

龍澤 2019-02-23 13:07:50

Flask 教程 第十九章：Docker容器上的部署

天降攻城獅 2019-02-23 10:17:16

docker

xmlgrg 2019-02-23 00:41:20

docker 基礎命令

qq5a3c5e337fedf 2019-02-23 00:40:07

docker容器初探—基本概念和基礎命令用法

IT陳工 2019-02-23 00:35:57

Docker的入門使用

二郎神六號 2019-02-23 00:33:25

部署落地+业务迁移 玩转k8s进阶与企业级实践技能

wy53780 2020-04-23 15:36:56

如何在 Kubernetes 環境中運行 Spark 集羣

JFrog中國 2019-02-23 00:34:06

Ubuntu 使用手記

zinejo 2019-02-23 13:50:25

ubuntu安裝jdk全過程

xiaovfight 2019-02-23 13:06:44

在Ubuntu 16.04上安裝Joomla系統

flygoooo 2019-02-23 00:33:54