kubeadm快速部署Kubernetes单节点
转载地址:https://www.cnblogs.com/Tempted/p/10671292.html
1. 安装要求
在开始之前,部署Kubernetes集群机器需要满足以下几个条件:
-
一台或多台机器,操作系统 CentOS7.x-86_x64
-
硬件配置:2GB或更多RAM,2个CPU或更多CPU,硬盘30GB或更多
-
集群中所有机器之间网络互通
-
可以访问外网,需要拉取镜像
-
禁止swap分区
2. 学习目标
-
在所有节点上安装Docker和kubeadm
-
部署Kubernetes Master
-
部署容器网络插件
-
部署 Kubernetes Node,将节点加入Kubernetes集群中
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
|
设置主机名$ hostnamectl set-hostname k8s-master$ hostnamectl set-hostname k8s-node1关闭防火墙:$ systemctl stop firewalld$ systemctl disable firewalld关闭selinux:$ sed -i 's/enforcing/disabled/' /etc/selinux/config$ setenforce 0关闭swap:$ swapoff -a $ 临时$ vim /etc/fstab $ 永久添加主机名与IP对应关系(记得设置主机名):cat <<EOF > /etc/hosts127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4::1 localhost localhost.localdomain localhost6 localhost6.localdomain6192.168.31.62 k8s-master192.168.31.63 k8s-node1EOF将桥接的IPv4流量传递到iptables的链:$ cat > /etc/sysctl.d/k8s.conf << EOFnet.bridge.bridge-nf-call-ip6tables = 1net.bridge.bridge-nf-call-iptables = 1EOF$ sysctl --system |
4. 所有节点安装Docker/kubeadm/kubelet
4.1 安装Docker
Kubernetes默认CRI(容器运行时)为Docker,因此先安装Docker。
|
1
2
3
4
5
|
$ wget https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo -O /etc/yum.repos.d/docker-ce.repo$ yum -y install docker-ce-18.06.1.ce-3.el7$ systemctl enable docker && systemctl start docker$ docker --versionDocker version 18.06.1-ce, build e68fc7a |
关于docker遇到的坑可以参考此篇文章:https://blog.csdn.net/zhonglinzhang/article/details/85254035
docker 加速镜像配置
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
|
$ mkdir /etc/docker/cat > /etc/docker/daemon.json <<EOF{ "exec-opts": ["native.cgroupdriver=cgroupfs"], "registry-mirrors": ["http://f1361db2.m.daocloud.io"], "log-driver": "json-file", "log-opts": { "max-size": "100m", "max-file":"3" }, "storage-driver": "overlay2", "storage-opts": [ "overlay2.override_kernel_check=true" ]}EOF# Restart docker.systemctl daemon-reloadsystemctl restart docker##max-file=3,意味着一个容器有三个日志,分别是id+.json、id+1.json、id+2.json尝试过修改kubelet的cgroup dirver(文件位置:/lib/systemd/system/kubelet.service.d/10-kubeadm.conf),但是每次启动kubeadm时会被覆盖掉,导致kubelet启动失败,只能修改docker的cgroup dirver设置;文档中docker驱动是systemd参考:https://kubernetes.io/docs/setup/production-environment/container-runtimes/ |
4.2 添加阿里云YUM软件源
|
1
2
3
4
5
6
7
8
9
|
$ cat > /etc/yum.repos.d/kubernetes.repo << EOF[kubernetes]name=Kubernetesbaseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64enabled=1gpgcheck=1repo_gpgcheck=1gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpgEOF |
4.3 安装kubeadm,kubelet和kubectl
这里安装最新版
|
1
2
|
$ yum install -y kubelet kubeadm kubectl$ systemctl enable kubelet |
5. 部署Kubernetes Master
|
1
2
3
4
5
6
|
kubeadm init \ --apiserver-advertise-address=192.168.124.195 \ --image-repository registry.aliyuncs.com/google_containers \ --kubernetes-version v1.14.0 \ --service-cidr=10.1.0.0/16\ --pod-network-cidr=10.244.0.0/16 |
这个初始化过程需要几分钟,具体时间取决于你的网络。
由于默认拉取镜像地址k8s.gcr.io国内无法访问,这里指定阿里云镜像仓库地址。
安装完成后根据提示操作
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
|
# 所有阶段会打印出来....Your Kubernetes master 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/configYou 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/You can now join any number of machines by running the following on each nodeas root: kubeadm join 192.168.124.194:6443 --token 4b3m3i.hrzetk4qb5uh74e4 --discovery-token-ca-cert-hash sha256:357b0fec02af903e66022019cea82ff3a95264479cb5d222ea8e938df2db3d20 |
给出一些下面要做的步骤,配置 kubectl, 配置网络组件,以及 worker node 加入的命令。
下面就是跟着提示配置 kubectl
|
1
2
3
|
mkdir -p $HOME/.kubesudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/configsudo chown $(id -u):$(id -g) $HOME/.kube/config |
或者,如果您是 root 用户,则可以运行:
export KUBECONFIG=/etc/kubernetes/admin.conf
可以看到 status 为 NotReady, 因为网络组件还没有配置, 下面配置 flannel。
|
1
2
3
|
[root@master ~]# kubectl get nodesNAME STATUS ROLES AGE VERSIONmaster NotReady master 1h v1.14.0 |
6. 安装Pod网络插件(CNI)
|
1
|
kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml |
如果下载quay.io镜像不成功可以修改为quay-mirror.qiniu.com 和 registry.aliyuncs.com
例如:
|
1
2
3
4
5
|
下拉镜像:quay.io/coreos/flannel:v0.10.0-s390x如果拉取较慢,可以改为:quay-mirror.qiniu.com/coreos/flannel:v0.10.0-s390x下拉镜像:gcr.io/google_containers/kube-proxy可以改为: registry.aliyuncs.com/google_containers/kube-proxy |
已修改的kube-flannel.yml
再来看状态
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
|
$ kubectl get pods --all-namespacesNAMESPACE NAME READY STATUS RESTARTS AGEkube-system coredns-78fcdf6894-4744c 1/1 Running 0 5mkube-system coredns-78fcdf6894-jbvhd 1/1 Running 0 5mkube-system kube-apiserver-master1 1/1 Running 0 5mkube-system kube-controller-manager-master1 1/1 Running 0 5mkube-system kube-flannel-ds-amd64-kp7cr 1/1 Running 0 11skube-system kube-proxy-6778v 1/1 Running 0 5mkube-system kube-scheduler-master1 1/1 Running 0 5m$ kubectl get nodesNAME STATUS ROLES AGE VERSIONmaster1 Ready master 1h v1.14.0$ kubectl get csNAME STATUS MESSAGE ERRORscheduler Healthy okcontroller-manager Healthy oketcd-0 Healthy {"health": "true"} |
|
1
2
3
4
5
6
|
在k8s最新版本 v1.16.3 你看到的是这样的$ kubectl get csNAME AGEcontroller-manager <unknown>scheduler <unknown>etcd-0 <unknown> |
开启master节点允许部署pod: kubectl taint nodes --all node-role.kubernetes.io/master-
不执行这条命令 创建会报错误:nodes are available: 1 node(s) had taints that the pod didn't tolerate.
master 节点的配置基本完成了。
Node 配置
就是执行之前 init 最后打出的那个命令
|
1
2
|
sudo kubeadm join 192.168.124.195:6443 --token qn1tr1.3xpu3qhu7ettn4gv \ --discovery-token-ca-cert-hash sha256:932f99ce7b294b63dd0f511da047c6ea9cf56fa9d8b4b1df9be70013b0c049c9 |
如果不幸,你忘记了上面的命令并且找不到了,可以通过 kubeadm token create --print-join-command 来获取
|
1
2
3
|
master复制admin文件到node节点scp /etc/kubernetes/admin.conf root@node1:/etc/kubernetes/admin.conf |
node操作完之后,再来 master 节点看看
|
1
2
3
4
|
$ kubectl get nodesNAME STATUS ROLES AGE VERSIONmaster1 Ready master 7m v1.14.0node1 Ready <none> 18s v1.14.0 |
用一个简单pod测试下
|
1
2
3
4
5
6
|
kubectl run -i --tty busybox --image=busybox --restart=Never -- sh# 正常执行,再看看调度情况$ kubectl get pod --show-all -o wideNAME READY STATUS RESTARTS AGE IP NODEbusybox 0/1 Completed 0 48s 10.244.1.2 node1 |
其他
|
1
2
3
4
5
6
7
8
9
10
11
12
13
|
master节点的token 24小时过期后,可以通过命令产生新的token:kubeadm token list创建永不过期的tokenkubeadm token create --ttl 0master节点上运行命令,可查询discovery-token-ca-cert-hash值:openssl x509 -pubkey -in /etc/kubernetes/pki/ca.crt | openssl rsa -pubin -outform der 2>/dev/null | openssl dgst -sha256 -hex | sed 's/^.* //'重新加入节点kubeadm join 192.168.124.195:6443 --token 8xwg8u.lkj382k9ox58qkw9 \--discovery-token-ca-cert-hash sha256:86291bed442dd1dcd6c26f2213208e10cab0f87763f44e0edf01fa670cd9e8b |
查看 kubeadm 的配置
kubeadm config view

浙公网安备 33010602011771号