172.22.139.245   k8s01    k8s01
172.22.139.243   k8s02    k8s02
172.22.139.242   k8s03    k8s03
172.22.139.244   k8s04    k8s04
复制

#!/bin/bash


#关闭防火墙，禁用防火墙开机自启动
systemctl stop firewalld
systemctl disable firewalld




# 临时禁用SeLinux，重启失效
setenforce 0
# 修改SeLinux配置，永久禁用
sed -i 's/^SELINUX=.*/SELINUX=disabled/' etc/selinux/config




# 临时关闭Swap
swapoff -a
# 修改 etc/fstab 删除或者注释掉swap的挂载，可永久关闭swap
sed -i '/swap/s/^/#/' etc/fstab




#修改k8s.conf
cat <<EOF > etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
sysctl --system
复制

#!/bin/bash




# 安装部分依赖
yum install -y yum-utils device-mapper-persistent-data lvm2
# 添加docker yum源
sudo yum-config-manager --add-repo http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
# 添加kubernetes yum源
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
# 对新添加的源的软件包信息cache一下
yum makecache -y
复制

#!/bin/bash


#安装docker
yum install -y docker-ce-*
#启动docker并设置开机自启动
systemctl enable docker
systemctl start docker




#安装kubernetes相关服务
yum install -y kubelet kubeadm kubectl
# 设置kuberlet为开机自启动
systemctl enable kubelet
systemctl start kubelet




#输出docker和kubernetes的信息
docker version
kubectl version
复制

journalctl -eu kubelet | less
复制

[root@k8s01 ~]# kubeadm init --apiserver-advertise-address=172.22.139.239 \
> --image-repository registry.aliyuncs.com/google_containers \
> --pod-network-cidr=10.244.0.0/16
[init] Using Kubernetes version: v1.22.1
[preflight] Running pre-flight checks
[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'
error execution phase preflight: [preflight] Some fatal errors occurred:
        [ERROR ImagePull]: failed to pull image registry.aliyuncs.com/google_containers/coredns:v1.8.4: output: Error response from daemon: manifest for registry.aliyuncs.com/google_containers/coredns:v1.8.4 not found: manifest unknown: manifest unknown
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher
复制

[root@k8s01 ~]# docker load -i coredns1.8.4.tar
225df95e717c: Loading layer  336.4kB/336.4kB
f72781b18181: Loading layer  47.34MB/47.34MB
Loaded image: coredns/coredns:1.8.4
[root@k8s01 ~]# docker tag coredns/coredns:1.8.4 registry.aliyuncs.com/google_containers/coredns:v1.8.4
[root@k8s01 ~]#
[root@k8s01 ~]# docker images
REPOSITORY        TAG       IMAGE ID       CREATED         SIZE
coredns/coredns   1.8.4     9a4aa3cc30a7   2 minutes ago   47.3MB
coredns/coredns   latest    8d147537fb7d   3 months ago    47.6MB
复制

Aug  6 21:14:41 localhost kubelet: E0806 21:14:41.164994   72318 server.go:294] "Failed to run kubelet" err="failed to run Kubelet: misconfiguration: kubelet cgroup driver: \"systemd\" is different from docker cgroup driver: \"cgroupfs\""
Aug  6 21:14:41 localhost systemd: kubelet.service: main process exited, code=exited, status=1/FAILURE
Aug  6 21:14:41 localhost systemd: Unit kubelet.service entered failed state.
Aug  6 21:14:41 localhost systemd: kubelet.service failed.
Aug  6 21:14:41 localhost systemd: Stopped kubelet: The Kubernetes Node Agent.
复制

echo y | kubeadm reset
[reset] Reading configuration from the cluster...
[reset] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
W0909 08:13:46.818026   18291 reset.go:101] [reset] Unable to fetch the kubeadm-config ConfigMap from cluster: failed to get config map: Get "https://172.22.139.239:6443/api/v1/namespaces/kube-system/configmaps/kubeadm-config?timeout=10s": dial tcp 172.22.139.239:6443: connect: connection refused
[reset] WARNING: Changes made to this host by 'kubeadm init' or 'kubeadm join' will be reverted.
[reset] Are you sure you want to proceed? [y/N]: [preflight] Running pre-flight checks
W0909 08:13:46.818165   18291 removeetcdmember.go:80] [reset] No kubeadm config, using etcd pod spec to get data directory
[reset] Stopping the kubelet service
[reset] Unmounting mounted directories in "/var/lib/kubelet"
[reset] Deleting contents of config directories: [/etc/kubernetes/manifests etc/kubernetes/pki]
[reset] Deleting files: [/etc/kubernetes/admin.conf etc/kubernetes/kubelet.conf etc/kubernetes/bootstrap-kubelet.conf etc/kubernetes/controller-manager.conf etc/kubernetes/scheduler.conf]
[reset] Deleting contents of stateful directories: [/var/lib/etcd var/lib/kubelet var/lib/dockershim var/run/kubernetes var/lib/cni]


The reset process does not clean CNI configuration. To do so, you must remove etc/cni/net.d


The reset process does not reset or clean up iptables rules or IPVS tables.
If you wish to reset iptables, you must do so manually by using the "iptables" command.




If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)
to reset your system's IPVS tables.




The reset process does not clean your kubeconfig files and you must remove them manually.
Please, check the contents of the $HOME/.kube/config file.
复制

[root@k8s01 ~]# cat etc/docker/daemon.json
{
  "registry-mirrors": ["https://w446wc4o.mirror.aliyuncs.com"],
  "exec-opts": ["native.cgroupdriver=systemd"]
}
复制

mkdir /var/lib/kubelet/
touch /var/lib/kubelet/config.yaml
cat > var/lib/kubelet/config.yaml <<EOF
apiVersion: kubelet.config.k8s.io/v1beta1
kind: KubeletConfiguration
cgroupDriver: systemd
EOF
复制

systemctl daemon-reload
systemctl restart docker
复制

echo y | kubeadm reset
复制

kubeadm init --apiserver-advertise-address=172.22.139.245 \
--image-repository registry.aliyuncs.com/google_containers \
--pod-network-cidr=10.244.0.0/16
复制

To start using your cluster, you need to run the following as a regular user:
#这三条命令在master节点依次执行
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
Alternatively, if you are the root user, you can run:
export KUBECONFIG=/etc/kubernetes/admin.conf
# 这个地方是说我们需要安装一个网络插件，我们接下来就会安装flannel网络
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:
#这个地方是其他worker节点加入该集群所要执行的命令，可以复制出来暂存一下，切记你要复制你自己主机上生成的
kubeadm join 192.168.56.111:6443 --token eud4cb.i6vf9rutybo9ve0u \
--discovery-token-ca-cert-hash sha256:dc89e4bf471b552e19b0c553910285014d93752398bbac7b6de23e455204c4aa
复制

Unable to connect to the server: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kubernetes")
复制

export KUBECONFIG=/etc/kubernetes/admin.conf




vi ~/.bash_profile
#add to env
export KUBECONFIG=/etc/kubernetes/admin.conf
复制

[root@k8s01 ~]# docker pull registry.cn-hangzhou.aliyuncs.com/k8sos/flannel:v0.14.0
v0.14.0: Pulling from k8sos/flannel
801bfaa63ef2: Pull complete
e4264a7179f6: Pull complete
bc75ea45ad2e: Pull complete
78648579d12a: Pull complete
3393447261e4: Pull complete
071b96dd834b: Pull complete
4de2f0468a91: Pull complete
Digest: sha256:e383a3714fb4f3d9b4c8ca84196745b887b59633f0577c105364a3b3f5e061b0
Status: Downloaded newer image for registry.cn-hangzhou.aliyuncs.com/k8sos/flannel:v0.14.0
registry.cn-hangzhou.aliyuncs.com/k8sos/flannel:v0.14.0
然后tag镜像名称，与kube-flannel.yml文件里相同
[root@k8s01 ~]# docker tag registry.cn-hangzhou.aliyuncs.com/k8sos/flannel:v0.14.0 quay.io/coreos/flannel:v0.14.0
复制

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

[root@k8s02 ~]# kubeadm join 172.22.139.239:6443 --token gcdxaj.3fc4i2dl2taihxxo         --discovery-token-ca-cert-hash sha256:16642fe5b55334bb760ea019d6d713b69ca34788cda6ea5e5958d3280702c49a
[preflight] Running pre-flight checks
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
[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] Starting the kubelet
[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.
复制

# 查看所有节点
kubectl get nodes
# 得到如下效果，三个节点均运行成功
# NAME STATUS ROLES AGE VERSION
# k8s111 Ready control-plane,master 14m v1.20.4
# k8s112 Ready <none> 24s v1.20.4
# k8s113 Ready <none> 14s v1.20.4
# 查看pods 集群搭建好，默认有一个kube-system命名空间，kubernetes自己的服务都部署在这个命名空间下
kubectl get pod -n kube-system
复制

docker pull registry.aliyuncs.com/google_containers/kube-controller-manager:v1.20.4
docker pull registry.aliyuncs.com/google_containers/kube-proxy:v1.20.4
docker pull registry.aliyuncs.com/google_containers/kube-apiserver:v1.20.4
docker pull registry.aliyuncs.com/google_containers/kube-scheduler:v1.20.4
docker pull registry.cn-hangzhou.aliyuncs.com/k8sos/flannel:v0.13.1-rc2
docker pull registry.aliyuncs.com/google_containers/etcd:3.4.13-0
docker pull registry.aliyuncs.com/google_containers/etcd:3.4.13-0
docker pull registry.aliyuncs.com/google_containers/coredns:1.7.0
docker pull registry.aliyuncs.com/google_containers/pause:3.2
复制