2. kubeadm部署kubernetes集羣— kubernetes入門到實戰【入門+進階篇】

時間  2020-05-25
標籤 kubeadm 部署 kubernetes 集羣 入門 實戰 入門+進階篇 欄目 負載均衡 简体版
原文   原文鏈接

1. kubernetes集羣部署

1.1 kubernetes安裝概述

要學習kubernetes，首先須要有一個kubernetes集羣，社區爲了知足不一樣場景下，提供了不一樣的安裝方法以適應各類場景需求，常見方法有：node

  • MiniKube，是一個將kubernetes單節點安裝在本地虛擬化工具，MiniKube安裝文檔
  • 二進制安裝，經過已編譯好的二進制文件安裝，需設置參數，可定製化強，安裝難度大
  • Kubeadm，一個自動化安裝工具，以鏡像的方式部署，使用簡單，鏡像在谷歌倉庫，下載易失敗

對於學習環境，Katacoda提供了一個在線的MiniKube環境，只需在控制檯啓用便可使用，固然也能夠將MiniKube下載到本地使用。對於生產環境，推薦使用二進制安裝或者Kubeadm，新版kubeadm目前已將kubernetes管理組件以pod的形式部署在集羣中，無論用哪一種方式，受限於GFW，大部分鏡像下載，你們自行補腦和解決，本文以離線的方式安裝部署。linux

1.2 kubernetes環境說明

安裝環境說明

【環境準備】git

一、設置主機名，其餘兩個節點相似設置github

root@VM_100_101_centos ~# hostnamectl set-hostname node-1
root@VM_100_101_centos ~# hostname
node-1

二、設置hosts文件，其餘兩個節點設置相同內容docker

root@node-1 ~# vim /etc/hosts
127.0.0.1 localhost localhost.localdomain 
10.211.55.201 node-1
10.211.55.202 node-2
10.211.55.203 node-3

三、設置SSH無密碼登陸，並經過ssh-copy-id將公鑰拷貝到對端shell

#生成密鑰對
root@node-1 .ssh# ssh-keygen -P ''
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): 
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:zultDMEL8bZmpbUjQahVjthVAcEkN929w5EkUmPkOrU root@node-1
The key's randomart image is:
+---RSA 2048----+
|      .=O=+=o.. |
|     o+o..+.o+  |
|    .oo=.   o. o |
|    . . * oo .+  |
|       oSOo.E  . |
|       oO.o.     |
|       o++ .     |
|       . .o      |
|        ...      |
+----SHA256-----+

#拷貝公鑰到node-2和node-3節點
root@node-1 .ssh# ssh-copy-id -i /root/.ssh/id_rsa.pub node-2:
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
The authenticity of host 'node-1 (10.254.100.101)' can't be established.
ECDSA key fingerprint is SHA256:jLUH0exgyJdsy0frw9R+FiWy+0o54LgB6dgVdfc6SEE.
ECDSA key fingerprint is MD5:f4:86:a8:0e:a6:03:fc:a6:04:df:91:d8:7a:a7:0d:9e.
Are you sure you want to continue connecting (yes/no)? yes
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
root@node-1's password: 
Number of key(s) added: 1
Now try logging into the machine, with:   "ssh 'node-2'"
and check to make sure that only the key(s) you wanted were added.

1.3 安裝docker

一、下載docker的yum源json

# wget -P /etc/yum.repos.d/ https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo

二、設置cgroup driver類型爲systemdbootstrap

[root@node-1 ~]# cat > /etc/docker/daemon.json <<EOF
> {
>  "exec-opts": ["native.cgroupdriver=systemd"],
>  "log-driver": "json-file",
>  "log-opts": {
>  "max-size": "100m"
>  },
>  "storage-driver": "overlay2",
>  "storage-opts": [
>  "overlay2.override_kernel_check=true"
>  ]
> }
> EOF

三、啓動docker服務並驗證，能夠經過docker info查看docker安裝的版本等信息vim

[root@node-1 ~]# systemctl restart docker
[root@node-1 ~]# systemctl enable docker

1.4 安裝kubeadm組件

一、安裝kubernetes源，國內可使用阿里的kubernetes源，速度會快一點centos

[root@node-1 ~]#cat <<EOF > /etc/yum.repos.d/kubernetes.repo
[kubernetes]
name=Kubernetes
baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg
EOF

二、安裝kubeadm，kubelet，kubectl，會自動安裝幾個重要依賴包：socat，cri-tools，cni等包

[root@node-1 ~]# yum install kubeadm kubectl  kubelet --disableexcludes=kubernetes -y

三、設置iptables網橋參數

[root@node-1 ~]# cat <<EOF >  /etc/sysctl.d/k8s.conf
> net.bridge.bridge-nf-call-ip6tables = 1
> net.bridge.bridge-nf-call-iptables = 1
> EOF

[root@node-1 ~]# sysctl --system,而後使用sysctl -a|grep 參數的方式驗證是否生效

四、從新啓動kubelet服務，使配置生效

[root@node-1 ~]# systemctl restart kubelet
[root@node-1 ~]# systemctl enable kubelet

1.5 導入kubernetes鏡像

一、從cos中下載kubernetes安裝鏡像，並經過docker load命令將鏡像導入到環境中

[root@node-1 v1.14.1]# docker image load -i etcd:3.3.10.tar 
[root@node-1 v1.14.1]# docker image load -i pause:3.1.tar 
[root@node-1 v1.14.1]# docker image load -i coredns:1.3.1.tar 
[root@node-1 v1.14.1]# docker image load -i flannel:v0.11.0-amd64.tar 
[root@node-1 v1.14.1]# docker image load -i kube-apiserver:v1.14.1.tar 
[root@node-1 v1.14.1]# docker image load -i kube-controller-manager:v1.14.1.tar 
[root@node-1 v1.14.1]# docker image load -i kube-scheduler:v1.14.1.tar 
[root@node-1 v1.14.1]# docker image load -i kube-proxy:v1.14.1.tar

二、檢查鏡像列表

[root@node-1 v1.14.1]# docker image list
REPOSITORY                           TAG                 IMAGE ID            CREATED             SIZE
k8s.gcr.io/kube-proxy                v1.14.1             20a2d7035165        3 months ago        82.1MB
k8s.gcr.io/kube-apiserver            v1.14.1             cfaa4ad74c37        3 months ago        210MB
k8s.gcr.io/kube-scheduler            v1.14.1             8931473d5bdb        3 months ago        81.6MB
k8s.gcr.io/kube-controller-manager   v1.14.1             efb3887b411d        3 months ago        158MB
quay.io/coreos/flannel               v0.11.0-amd64       ff281650a721        6 months ago        52.6MB
k8s.gcr.io/coredns                   1.3.1               eb516548c180        6 months ago        40.3MB
k8s.gcr.io/etcd                      3.3.10              2c4adeb21b4f        8 months ago        258MB
k8s.gcr.io/pause                     3.1                 da86e6ba6ca1        19 months ago       742kB

1.6 kubeadm初始化集羣

初始化過程

一、 kubeadm初始化集羣，須要設置初始參數

  • --pod-network-cidr指定pod使用的網段，設置值根據不一樣的網絡plugin選擇，本文以flannel爲例設置值爲10.244.0.0/16
  • container runtime能夠經過--cri-socket指定socket文件所屬路徑
  • 若是有多個網卡能夠經過--apiserver-advertise-address指定master地址，默認會選擇訪問外網的ip
[root@node-1 ~]# kubeadm init --apiserver-advertise-address 10.254.100.101 --apiserver-bind-port 6443  --pod-network-cidr 10.244.0.0/16
[init] Using Kubernetes version: v1.14.1
[preflight] Running pre-flight checks
 [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 18.03.1-ce. Latest validated version: 18.09
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'#下載鏡像
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Activating the kubelet service
[certs] Using certificateDir folder "/etc/kubernetes/pki"#生成CA等證書
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [node-1 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.254.100.101]
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [node-1 localhost] and IPs [10.254.100.101 127.0.0.1 ::1]
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [node-1 localhost] and IPs [10.254.100.101 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[control-plane] Using manifest folder "/etc/kubernetes/manifests"#生成master節點靜態pod配置文件
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[apiclient] All control plane components are healthy after 18.012370 seconds
[upload-config] storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.14" in namespace kube-system with the configuration for the kubelets in the cluster
[upload-certs] Skipping phase. Please see --experimental-upload-certs
[mark-control-plane] Marking the node node-1 as control-plane by adding the label "node-role.kubernetes.io/master=''"
[mark-control-plane] Marking the node node-1 as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
[bootstrap-token] Using token: r8n5f2.9mic7opmrwjakled
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles#配置RBAC受權
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstrap-token] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstrap-token] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstrap-token] creating the "cluster-info" ConfigMap in the "kube-public" namespace
[addons] Applied essential addon: CoreDNS
[addons] Applied essential addon: kube-proxy
Your Kubernetes control-plane has initialized successfully!
To start using your cluster, you need to run the following as a regular user:
 mkdir -p $HOME/.kube #配置環境變量配置文件
 sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
 sudo chown $(id -u):$(id -g) $HOME/.kube/config
You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at: #安裝網絡插件
 https://kubernetes.io/docs/concepts/cluster-administration/addons/
Then you can join any number of worker nodes by running the following on each as root:
kubeadm join 10.254.100.101:6443 --token r8n5f2.9mic7opmrwjakled \ #添加節點命令，優先記錄下來
 --discovery-token-ca-cert-hash sha256:16e383c8abff6233021331944080087f0514ddd15d96c65d19443b0af02d64ab

經過kubeadm init --apiserver-advertise-address 10.254.100.101 --apiserver-bind-port 6443 --kubernetes-version 1.14.1 --pod-network-cidr 10.244.0.0/16安裝命令，顯示了kubeadm安裝過程當中的一些重要步驟：下載鏡像，生成證書，生成配置文件，配置RBAC受權認證，配置環境變量，安裝網絡插件指引，添加node指引配置文件。

二、生成kubectl環境配置文件

[root@node-1 ~]# mkdir /root/.kube
[root@node-1 ~]# cp -i /etc/kubernetes/admin.conf /root/.kube/config
[root@node-1 ~]# kubectl get nodes
NAME  STATUS  ROLES AGE  VERSION
node-1  NotReady  master  6m29s  v1.14.1

三、添加node節點，將另外兩個節點加入到集羣中，複製上述的添加節點命令到指定節點添加便可。

[root@node-3 ~]# kubeadm join 10.254.100.101:6443 --token r8n5f2.9mic7opmrwjakled \
>     --discovery-token-ca-cert-hash sha256:16e383c8abff6233021331944080087f0514ddd15d96c65d19443b0af02d64ab 
[preflight] Running pre-flight checks
    [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 18.03.1-ce. Latest validated version: 18.09
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[kubelet-start] Downloading configuration for the kubelet from the "kubelet-config-1.14" ConfigMap in the kube-system namespace
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Activating the kubelet service
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...

This node has joined the cluster:
* Certificate signing request was sent to apiserver and a response was received.
* The Kubelet was informed of the new secure connection details.

Run 'kubectl get nodes' on the control-plane to see this node join the cluster.

以此類推到node-2節點添加便可，添加完以後經過kubectl get nodes驗證，此時因爲尚未安裝網絡plugin，
全部的node節點均顯示NotReady狀態：
[root@node-1 ~]# kubectl get nodes
NAME     STATUS     ROLES    AGE     VERSION
node-1   NotReady   master   16m     v1.14.1
node-2   NotReady   <none>   4m34s   v1.14.1
node-3   NotReady   <none>   2m10s   v1.14.1

添加節點

四、安裝網絡plugin，kubernetes支持多種類型網絡插件，要求網絡支持CNI插件便可，CNI是Container Network Interface，要求kubernetes的中pod網絡訪問方式：

  • node和node之間網絡互通
  • pod和pod之間網絡互通
  • node和pod之間網絡互通

不一樣的CNI plugin支持的特性有所差異。kubernetes支持多種開源的網絡CNI插件，常見的有flannel、calico、canal、weave等，flannel是一種overlay的網絡模型，經過vxlan隧道方式構建tunnel網絡，實現k8s中網絡的互聯，後續在作介紹，以下是安裝過程：

[root@node-1 ~]# kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/62e44c867a2846fefb68bd5f178daf4da3095ccb/Documentation/kube-flannel.yml
podsecuritypolicy.extensions/psp.flannel.unprivileged created
clusterrole.rbac.authorization.k8s.io/flannel created
clusterrolebinding.rbac.authorization.k8s.io/flannel created
serviceaccount/flannel created
configmap/kube-flannel-cfg created
daemonset.extensions/kube-flannel-ds-amd64 created
daemonset.extensions/kube-flannel-ds-arm64 created
daemonset.extensions/kube-flannel-ds-arm created
daemonset.extensions/kube-flannel-ds-ppc64le created
daemonset.extensions/kube-flannel-ds-s390x created

五、經過上述輸出可知道，部署flannel 須要RBAC受權，配置configmap和daemonset，其中Daemonset可以適配各類類型的CPU架構，默認安裝了多個，通常是adm64便可，能夠將上述的url下載編輯，保留kube-flannel-ds-amd64這個daemonset便可，或者將其刪除

#查看flannel安裝的daemonsets
[root@node-1 ~]# kubectl get daemonsets -n kube-system 
NAME                      DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR                     AGE
kube-flannel-ds-amd64     3         3         3       3            3           beta.kubernetes.io/arch=amd64     2m34s
kube-flannel-ds-arm       0         0         0       0            0           beta.kubernetes.io/arch=arm       2m34s
kube-flannel-ds-arm64     0         0         0       0            0           beta.kubernetes.io/arch=arm64     2m34s
kube-flannel-ds-ppc64le   0         0         0       0            0           beta.kubernetes.io/arch=ppc64le   2m34s
kube-flannel-ds-s390x     0         0         0       0            0           beta.kubernetes.io/arch=s390x     2m34s
kube-proxy                3         3         3       3            3           <none>                            30m

#刪除不須要的damonsets
[root@node-1 ~]# kubectl delete daemonsets kube-flannel-ds-arm kube-flannel-ds-arm64 kube-flannel-ds-ppc64le kube-flannel-ds-s390x -n kube-system
daemonset.extensions "kube-flannel-ds-arm" deleted
daemonset.extensions "kube-flannel-ds-arm64" deleted
daemonset.extensions "kube-flannel-ds-ppc64le" deleted
daemonset.extensions "kube-flannel-ds-s390x" deleted

六、此時再驗證node的安裝狀況,全部節點均已顯示爲Ready狀態，安裝完畢！

[root@node-1 ~]# kubectl get nodes
NAME     STATUS   ROLES    AGE   VERSION
node-1   Ready    master   29m   v1.14.1
node-2   Ready    <none>   17m   v1.14.1
node-3   Ready    <none>   15m   v1.14.1

1.7 驗證kubernetes組件

一、驗證node狀態，獲取當前安裝節點，能夠查看到狀態， 角色，啓動市場，版本，

[root@node-1 ~]# kubectl get nodes 
NAME     STATUS   ROLES    AGE   VERSION
node-1   Ready    master   46m   v1.14.1
node-2   Ready    <none>   34m   v1.14.1
node-3   Ready    <none>   32m   v1.14.1

二、查看kubernetse服務組件狀態,包括scheduler，controller-manager，etcd

[root@node-1 ~]# kubectl get componentstatuses 
NAME  STATUS MESSAGE  ERROR
scheduler Healthy  ok  
controller-manager  Healthy  ok  
etcd-0  Healthy  {"health":"true"}

三、查看pod的狀況,master中的角色包括kube-apiserver，kube-scheduler，kube-controller-manager，etcd，coredns以pods形式部署在集羣中，worker節點的kube-proxy也以pod的形式部署。實際上pod是以其餘控制器如daemonset的形式控制的。

[root@node-1 ~]# kubectl get pods -n kube-system 
NAME  READY  STATUS RESTARTS  AGE
coredns-fb8b8dccf-hrqm8 1/1  Running  0 50m
coredns-fb8b8dccf-qwwks 1/1  Running  0 50m
etcd-node-1 1/1  Running  0 48m
kube-apiserver-node-1 1/1  Running  0 49m
kube-controller-manager-node-1  1/1  Running  0 49m
kube-proxy-lfckv  1/1  Running  0 38m
kube-proxy-x5t6r  1/1  Running  0 50m
kube-proxy-x8zqh  1/1  Running  0 36m
kube-scheduler-node-1 1/1  Running  0 49m

1.8 配置kubectl命令補全

使用kubectl和kubernetes交互時候可使用縮寫模式也可使用完整模式，如kubectl get nodes和kubectl get no能實現同樣的效果，爲了提升工做效率，可使用命令補全的方式加快工做效率。

一、生成kubectl bash命令行補全shell

[root@node-1 ~]# kubectl completion bash >/etc/kubernetes/kubectl.sh
[root@node-1 ~]# echo "source /etc/kubernetes/kubectl.sh" >>/root/.bashrc 
[root@node-1 ~]# cat /root/.bashrc 
# .bashrc

# User specific aliases and functions

alias rm='rm -i'
alias cp='cp -i'
alias mv='mv -i'

# Source global definitions
if [ -f /etc/bashrc ]; then
    . /etc/bashrc
fi
source /etc/kubernetes/kubectl.sh #添加環境變量配置

二、加載shell環境變量，使配置生效

[root@node-1 ~]# source /etc/kubernetes/kubectl.sh

三、校驗命令行補全，命令行中輸入kubectl get co再按TAB鍵就能自動補全了 

[root@node-1~]# kubectl get co componentstatuses configmaps  controllerrevisions.apps   
[root@node-1~]# kubectl get componentstatuses

除了支持命令行補全以外，kubectl還支持命令簡寫，以下是一些常見的命令行檢測操做,更多經過kubectl api-resources命令獲取，SHORTNAMES顯示的是子命令中的簡短用法。

  • kubectl get componentstatuses，簡寫kubectl get cs獲取組件狀態
  • kubectl get nodes，簡寫kubectl get no獲取node節點列表
  • kubectl get services，簡寫kubectl get svc獲取服務列表
  • kubectl get deployments,簡寫kubectl get deploy獲取deployment列表
  • kubectl get statefulsets,簡寫kubectl get sts獲取有狀態服務列表

參考文檔

  1. Container Runtime安裝文檔：https://kubernetes.io/docs/setup/production-environment/container-runtimes/
  2. kubeadm安裝：https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/
  3. 初始化kubeadm集羣：https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#pod-network
相關文章
相關標籤/搜索
每日一句
    每一个你不满意的现在，都有一个你没有努力的曾经。
本站公眾號
   歡迎關注本站公眾號,獲取更多信息
聯繫我們 最近搜索 最新文章 沪ICP备13005482号-10 MyBatis教程 SQL 教程 MySQL教程 Java 教程 Thymeleaf 教程 Hibernate教程 Spring教程 Redis教程