Kubernetes系列（一）基于CentOS8部署Kubernetes1.19集群

1.系统环境

系统版本：CentOS8.1.1911
Kubernetes版本：1.19.1
Docker版本：19.03.1
节点信息：
10.24.10.3 master
10.24.10.6 node1
10.24.10.11 node2
10.24.10.16 node3

---

2.基础环境

2.1 配置主机映射

所有节点配置主机映射：

# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
10.24.10.3  master
10.24.10.6  node1
10.24.10.11 node2
10.24.10.16 node3

---

2.2 关闭Swap分区

所有节点关闭swap分区：

# swapoff -a
# sed -i 's/.*swap.*/#&/' /etc/fstab

---

2.3 配置SELinx和防火墙

所有节点关闭SELinux：

# setenforce 0
# sed -i "s/^SELINUX=enforcing/SELINUX=disabled/g" /etc/selinux/config

所有节点关闭防火墙：

# systemctl stop firewalld
# systemctl disable firewalld

---

2.4 配置内核参数

所有节点配置内核参数，将桥接的IPv4流量传递到iptables的链：

# cat << EOF | tee /etc/sysctl.d/k8s.conf
net.ipv4.ip_forward = 1
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
# modprobe br_netfilter
# sysctl -p /etc/sysctl.d/k8s.conf

---

2.5 安装Docker

所有节点安装基础工具包：

# yum install vim bash-completion net-tools gcc -y

所有节点安装Docker CE：

# yum install -y yum-utils device-mapper-persistent-data lvm2
# yum-config-manager --add-repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
# yum install wget container-selinux -y
# wget https://download.docker.com/linux/centos/7/x86_64/stable/Packages/containerd.io-1.4.3-3.1.el7.x86_64.rpm
# yum erase runc -y
# rpm -ivh containerd.io-1.4.3-3.1.el7.x86_64.rpm
# yum install -y docker-ce-19.03.1

所有节点配置Docker并启动：

# mkdir -p /etc/docker
# tee /etc/docker/daemon.json << EOF
{
  "insecure-registries" : ["0.0.0.0/0"],
  "registry-mirrors": ["https://5twf62k1.mirror.aliyuncs.com"]
}
EOF
# systemctl daemon-reload && systemctl start docker && systemctl enable docker

---

2.6 安装Kubernetes工具

所有节点安装kubernetes工具：

# 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
# yum install kubectl-1.19.1 kubelet-1.19.1 kubeadm-1.19.1 -y
# systemctl enable kubelet

至此基础环境就准备完成了。

---

3.部署Kubernetes集群

3.1 初始化集群

在master节点执行初始化集群命令：

[root@master ~]# kubeadm init --apiserver-advertise-address=10.24.10.3 \
--image-repository=registry.aliyuncs.com/google_containers \
--kubernetes-version=v1.19.1 \
--pod-network-cidr=10.122.0.0/16
W0113 07:55:40.478218   22739 configset.go:348] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[init] Using Kubernetes version: v1.19.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/
        [WARNING FileExisting-tc]: tc not found in system path
[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'
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local master] and IPs [10.96.0.1 10.24.10.3]
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-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 [localhost master] and IPs [10.24.10.3 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [localhost master] and IPs [10.24.10.3 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-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
[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] Starting the kubelet
[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 16.504392 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.19" 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 master as control-plane by adding the label "node-role.kubernetes.io/master=''"
[mark-control-plane] Marking the node master as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
[bootstrap-token] Using token: x5muib.7fzqe05ytz471354
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to get nodes
[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
[kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key
[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.24.10.3:6443 --token x5muib.7fzqe05ytz471354 \
    --discovery-token-ca-cert-hash sha256:03efc1126c50139ba9aa762ad79e1f916be937521eccc02316ae4a29534ad9eb

记录生成信息最后部分的内容，此内容需要在其它节点加入Kubernetes集群时执行。
根据提示配置kubectl：

[root@master ~]# mkdir -p $HOME/.kube
[root@master ~]# sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
[root@master ~]# sudo chown $(id -u):$(id -g) $HOME/.kube/config

所有node节点加入集群：

# kubeadm join 10.24.10.3:6443 --token x5muib.7fzqe05ytz471354 \
    --discovery-token-ca-cert-hash sha256:03efc1126c50139ba9aa762ad79e1f916be937521eccc02316ae4a29534ad9eb

查看集群节点状态：

[root@master ~]# kubectl get nodes
NAME       STATUS       ROLES     AGE       VERSION
master     NotReady     master    4m16s     v1.19.1
node1      NotReady     <none>    59s       v1.19.1
node2      NotReady     <none>    53s       v1.19.1
node3      NotReady     <none>    52s       v1.19.1

所有节点状态都为NotReady，因为coredns Pod没有启动。

---

3.2 安装网络

安装calico网络：

[root@master ~]# kubectl apply -f https://docs.projectcalico.org/manifests/calico.yaml
configmap/calico-config created
customresourcedefinition.apiextensions.k8s.io/bgpconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/bgppeers.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/blockaffinities.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/clusterinformations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/felixconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/globalnetworkpolicies.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/globalnetworksets.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/hostendpoints.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamblocks.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamconfigs.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamhandles.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ippools.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/kubecontrollersconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/networkpolicies.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/networksets.crd.projectcalico.org created
clusterrole.rbac.authorization.k8s.io/calico-kube-controllers created
clusterrolebinding.rbac.authorization.k8s.io/calico-kube-controllers created
clusterrole.rbac.authorization.k8s.io/calico-node created
clusterrolebinding.rbac.authorization.k8s.io/calico-node created
daemonset.apps/calico-node created
serviceaccount/calico-node created
deployment.apps/calico-kube-controllers created
serviceaccount/calico-kube-controllers created
poddisruptionbudget.policy/calico-kube-controllers created

查看Pod状态：

[root@master ~]# kubectl -n kube-system get pods
NAME                                       READY   STATUS    RESTARTS   AGE
calico-kube-controllers-744cfdf676-p7jdp   1/1        Running    0          2m32s
calico-node-4vzp2                          1/1        Running    0          2m32s
calico-node-f5kq8                          1/1        Running    0          2m32s
calico-node-fg8mx                          1/1        Running    0          2m32s
calico-node-s5hxc                          1/1        Running    0          2m32s
coredns-6d56c8448f-d4b62                   1/1        Running    0          8m23s
coredns-6d56c8448f-qq7z8                   1/1        Running    0          8m23s
etcd-master                                1/1        Running    0         8m35s
kube-apiserver-master                      1/1        Running    0          8m35s
kube-controller-manager-master             1/1        Running    0          8m35s
kube-proxy-6l64k                           1/1        Running    0          5m18s
kube-proxy-hgcn8                           1/1        Running    0          8m23s
kube-proxy-mr8fm                           1/1        Running    0         5m19s
kube-proxy-prbsb                           1/1        Running    0         5m25s
kube-scheduler-master                      1/1        Running    0         8m35s

所有集群节点状态：

[root@master ~]# kubectl get nodes
NAME     STATUS    ROLES      AGE      VERSION
master   Ready     master     10m      v1.19.1
node1    Ready     <none>     7m28s    v1.19.1
node2    Ready     <none>     7m22s    v1.19.1
node3    Ready     <none>     7m21s    v1.19.1

至此，Kubernetes1.19集群就部署完成了。

---

4.FAQ

4.1 集群状态Unhealthy

查看集群状态：

[root@master ~]# kubectl get cs
NAME                 STATUS      MESSAGE              ERROR
controller-manager   Unhealthy   Get "http://127.0.0.1:10252/healthz": dial tcp 127.0.0.1:10252: connect: connection refused   
scheduler            Unhealthy   Get "http://127.0.0.1:10251/healthz": dial tcp 127.0.0.1:10251: connect: connection refused   
etcd-0               Healthy     {"health":"true"}

---

出现这种情况是因为/etc/kubernetes/manifests目录下的kube-controller-manager.yaml和kube-scheduler.yaml设置的默认端口是0，在文件中注释掉就可以了。
修改kube-controller-manager.yaml文件，注释掉第27行“- --port=0”。
修改kube-scheduler.yaml文件，注释掉第19行“- --port=0”。
所有节点重启kubelet：

# systemctl restart kubelet

再次查看集群状态就正常了：

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

---

4.2 删除namespace一直处于Terminating状态

创建api proxy：

# kubectl proxy --port=8081

把ns追加到json文件：

# kubectl get namespace xxxx -o json |jq '.spec = {"finalizers":[]}' >temp.json

调用api删除：

# curl -k -H "Content-Type: application/json" -X PUT --data-binary @temp.json 127.0.0.1:8081/api/v1/namespaces/xxxx/finalize

---