Ubuntu16.04安裝K8s步驟和踩坑記錄-修改版本，k8s 最新版本1.15.1

文章轉載自冰糖大佬的部落格，不過他的版本是1.13xxx的，我安裝的是最新版，一路踩了各種坑，各種百度，然後在巨人的肩膀上修改了大佬文章，并添加了我遇到的錯誤，如果有安裝1.13版本左右的，可以直接檢視大佬的版本，原文章清晰格式工整，連結如下：

https://blog.csdn.net/wangchunfa122/article/details/86529406

----------------------我的修訂版本開始了---------------------------------------

環境資訊

安裝步驟

系統配置修改

安裝docker

安裝kubectl，kubelet，kubeadm

配置Master

配置Node

部署結果檢查

K8S部署mysql學習

建立mysql-rc.yaml

建立mysql-svc.yaml

安裝

K8S部署JAVA應用

建立deployment

建立service

更新deployment

其他指令

環境資訊

名稱：版本

Docker 18.06.1-ce

作業系統 Ubuntu16.04

K8s v1.13.2

機器資訊

IP 作用元件

10.2.14.78 Master

10.2.14.79 Node

10.2.14.80 Node

安裝步驟

系統配置修改

禁用swap

swapoff -a

同時把/etc/fstab包含swap那行記錄删掉。

關閉防火牆

systemctl stop firewalld

systemctl disable firewalld

禁用Selinux

apt install selinux-utils

setenforce 0

各主機的主機名及ip配置。

本次實戰中一共用到二台主機，一台用于Master的部署，上司兩台分别為node1。主機名和IP的對應關系如下：

192.168.26.131 nuke-k8s-m

192.168.26.132 nuke-k8s-n

同時在每台機器的/etc/hosts配置如下

192.168.26.131 nuke-k8s-m

192.168.26.132 nuke-k8s-n

安裝docker

在Master和Node節點分别執行如下操作

先安裝相關工具

apt-get update && apt-get install -y apt-transport-https curl

添加密鑰

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | apt-key add -

安轉docker

apt-get install docker.io -y

檢視docker版本

[email protected]:~# docker version

Client:

Version: 18.09.7

API version: 1.39

Go version: go1.10.4

Git commit: 2d0083d

Built: Wed Jul 3 13:38:22 2019

OS/Arch: linux/amd64

Experimental: false

Server:

Engine:

Version: 18.09.7

API version: 1.39 (minimum version 1.12)

Go version: go1.10.4

Git commit: 2d0083d

Built: Mon Jul 1 19:31:53 2019

OS/Arch: linux/amd64

Experimental: false

啟動docker service

systemctl enable docker
systemctl start docker
systemctl status docker

修改檔案

vim  /etc/docker/daemon.json
{
    "registry-mirrors": ["https://alzgoonw.mirror.aliyuncs.com"],
    "live-restore": true
}

重起docker服務

systemctl daemon-reload
systemctl restart docker

安裝kubectl，kubelet，kubeadm

在Master和Node節點分别執行如下操作

接下來添加秘鑰

國内隻能用這個

curl -s https://mirrors.aliyun.com/kubernetes/apt/doc/apt-key.gpg| sudo apt-key add -

添加Kubernetes軟體源

cat <<EOF >/etc/apt/sources.list.d/kubernetes.list
deb http://apt.kubernetes.io/ kubernetes-xenial main
EOF

上面是官方的源，國内不通需要修改為如下

cat <<EOF >/etc/apt/sources.list.d/kubernetes.list

deb http://mirrors.ustc.edu.cn/kubernetes/apt kubernetes-xenial main

EOF

安裝

# apt-get update && apt-get install -y kubelet kubeadm kubectl
# systemctl enable kubelet

– 修改源—

問題：apt-get update 錯誤逾時，被牆了。需要修改apt-get的源，采用ustc源

vim /etc/apt/sources.list.d/kubernetes.list

增加内容如下，然後重新安裝

# deb http://apt.kubernetes.io/ kubernetes-xenial main

deb http://mirrors.ustc.edu.cn/kubernetes/apt kubernetes-xenial main

注：ubuntu16.04 代号為xenial

配置Master

在/etc/profile 下面增加如下環境變量

export KUBECONFIG=/etc/kubernetes/admin.conf

*暫時沒有這個檔案，不要擔心，就照着做就行

# 重起kubelet

systemctl daemon-reload

systemctl restart kubelet

在master節點上執行

kubeadm init --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=10.2.14.78 --kubernetes-version=v1.15.1 --ignore-preflight-errors=Swap

–pod-network-cidr是指配置節點中的pod的可用IP位址，此為内部IP

–apiserver-advertise-address 為master的IP位址

–kubernetes-version 通過kubectl version 可以檢視到

不幸的是報錯, k8s.gcr.io 被牆了，鏡像下載下傳失敗

[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'

error execution phase preflight: [preflight] Some fatal errors occurred:

[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.13.2: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

, error: exit status 1

........

根據報錯資訊，在國内網站站上找到相關的鏡像(docker需要配置阿裡雲的鏡像倉庫)

看版本，我用的時1.15.1

docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.13.2

docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.13.2

docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.13.2

docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.1

docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.2.24

docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.2.6

docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.13.2

docker tag gcr.azk8s.cn/google-containers/kube-apiserver:v1.15.1 k8s.gcr.io/kube-apiserver:v1.15.1

docker tag gcr.azk8s.cn/google-containers/kube-controller-manager:v1.15.1 k8s.gcr.io/kube-controller-manager:v1.15.1

docker tag gcr.azk8s.cn/google-containers/kube-scheduler:v1.15.1 k8s.gcr.io/kube-scheduler:v1.15.1

docker tag gcr.azk8s.cn/google-containers/kube-proxy:v1.15.1 k8s.gcr.io/kube-proxy:v1.15.1

docker tag gcr.azk8s.cn/google-containers/pause:3.1 k8s.gcr.io/pause:3.1

docker tag gcr.azk8s.cn/google-containers/etcd:3.3.10 k8s.gcr.io/etcd:3.3.10

docker tag gcr.azk8s.cn/google-containers/coredns:1.3.1 k8s.gcr.io/coredns:1.3.1

重新執行

kubeadm init --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=192.168.26.131 --kubernetes-version=v1.15.1 --ignore-preflight-errors=Swap

輸出結果如下，其中最後一行是節點加入master叢集需要的指令

[email protected]:/home/nuke# kubeadm init --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=192.168.26.131 --kubernetes-version=v1.15.1 --ignore-preflight-errors=Swap

[init] Using Kubernetes version: v1.15.1

[preflight] Running pre-flight checks

[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/

[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"

[certs] Generating "etcd/ca" certificate and key

[certs] Generating "apiserver-etcd-client" certificate and key

[certs] Generating "etcd/server" certificate and key

[certs] etcd/server serving cert is signed for DNS names [nuke1 localhost] and IPs [192.168.26.131 127.0.0.1 ::1]

[certs] Generating "etcd/peer" certificate and key

[certs] etcd/peer serving cert is signed for DNS names [nuke1 localhost] and IPs [192.168.26.131 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 "ca" certificate and key

[certs] Generating "apiserver-kubelet-client" certificate and key

[certs] Generating "apiserver" certificate and key

[certs] apiserver serving cert is signed for DNS names [nuke1 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 192.168.26.131]

[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"

[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 28.520233 seconds

[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace

[kubelet] Creating a ConfigMap "kubelet-config-1.15" in namespace kube-system with the configuration for the kubelets in the cluster

[upload-certs] Skipping phase. Please see --upload-certs

[mark-control-plane] Marking the node nuke1 as control-plane by adding the label "node-role.kubernetes.io/master=''"

[mark-control-plane] Marking the node nuke1 as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]

[bootstrap-token] Using token: 13zy98.ubjskmoo7rqthc4n

[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles

[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 192.168.26.131:6443 --token 13zy98.ubjskmoo7rqthc4n \

--discovery-token-ca-cert-hash sha256:5a2fbd7d74327c3ea716835fc49cb2cf8d9db3ec29af2925812cbc4b811d8383

[email protected]:/home/nuke# mkdir -p $HOME/.kube

[email protected]:/home/nuke# sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config

[email protected]:/home/nuke# sudo chown $(id -u):$(id -g) $HOME/.kube/config

在安裝完Master節點後，檢視節點資訊（

kubectl get nodes

)會發現節點的狀态為noready。檢視noready的原因發現是由于cni插件沒有配置。其實這是由于還沒有配置網絡。可以配置多種網絡，這裡作者選用最長遠的fannel網絡進行配置。

kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml

配置Node

在各個node節點執行如下指令（對應master配置傳回的 kubeadm join指令），加入master叢集-- 這個就是master啟動完的最後一句指令

kubeadm join 192.168.26.131:6443 --token 13zy98.ubjskmoo7rqthc4n \

--discovery-token-ca-cert-hash sha256:5a2fbd7d74327c3ea716835fc49cb2cf8d9db3ec29af2925812cbc4b811d8383

在master檢視nodes狀态，Node的狀态為NotReady

[email protected]:~# kk get nodes

NAME STATUS ROLES AGE VERSION

nuke1 Ready master 105m v1.15.1

nuke2 NotReady <none> 102m v1.15.1

檢視pod狀态，部分服務沒有正常啟動，原因是各個node也缺少鏡像，需要手動下載下傳，按照在master手動下載下傳鏡像的方式下載下傳即可，再node上執行：