腾云搭建k8s

1、三台主机分别修改主机名：【vi /etc/hosts】
master 10.20.0.128 hostnamectl set-hostname master
node1 10.20.0.129 hostnamectl set-hostname node1
node2 10.20.0.130 hostnamectl set-hostname node2

2、三台都修改vi /etc/hosts文件，加入主机名解析【vi /etc/hosts】
10.10.0.128 master
10.10.0.129 node1
10.10.0.130 node2

3、三台主机均关闭防火墙，selinux，并关闭swap分区
swapoff -a
sed -ri ‘s/.swap./#&/’ /etc/fstab
systemctl stop firewalld
systemctl disable firewalld
sed -i ‘s/enforcing/disabled/’ /etc/selinux/config
setenforce 0
echo "net.bridge.bridge-nf-call-iptables = 1 ">>/etc/sysctl.d/k8s.conf
echo "net.bridge.bridge-nf-call-ip6tables = 1 ">>/etc/sysctl.d/k8s.conf
sysctl --system
开启net.bridge.bridge-nf-call-iptables＝1，意味着二层的网桥在转发包时也会被iptables的FORWARD规则所过滤

4、所有节点安装docker并启用docker
wget https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo -O /etc/yum.repos.d/docker-ce.repo
yum install docker-ce
systemctl enable docker
systemctl start docker
docker version

5、所有节点均安装并启用kubelet kubeadm kubectl

cat < /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 -y kubelet kubeadm kubectl
systemctl enable kubelet
systemctl start kubelet

6、查看需要拉取的镜像，并拉取镜像。
kubeadm config images list

master拉取镜像：
docker pull registry.aliyuncs.com/google_containers/kube-apiserver:v1.21.1
docker pull registry.aliyuncs.com/google_containers/kube-controller-manager:v1.21.1
docker pull registry.aliyuncs.com/google_containers/kube-scheduler:v1.21.1
docker pull registry.aliyuncs.com/google_containers/kube-proxy:v1.21.1
docker pull registry.aliyuncs.com/google_containers/pause:3.4.1
docker pull registry.aliyuncs.com/google_containers/etcd:3.4.13-0
docker pull registry.aliyuncs.com/google_containers/coredns:1.8.0

修改标签：
docker tag registry.aliyuncs.com/google_containers/kube-apiserver:v1.21.1 k8s.gcr.io/kube-apiserver:v1.21.1
docker tag registry.aliyuncs.com/google_containers/kube-controller-manager:v1.21.1 k8s.gcr.io/kube-controller-manager:v1.21.1
docker tag registry.aliyuncs.com/google_containers/kube-scheduler:v1.21.1 k8s.gcr.io/kube-scheduler:v1.21.1
docker tag registry.aliyuncs.com/google_containers/kube-proxy:v1.21.1 k8s.gcr.io/kube-proxy:v1.21.1
docker tag registry.aliyuncs.com/google_containers/pause:3.4.1 k8s.gcr.io/pause:3.4.1
docker tag registry.aliyuncs.com/google_containers/etcd:3.4.13-0 k8s.gcr.io/etcd:3.4.13-0
docker tag registry.aliyuncs.com/google_containers/coredns:1.8.0 k8s.gcr.io/coredns:1.8.0

删除历史镜像：
docker rmi registry.aliyuncs.com/google_containers/kube-apiserver:v1.21.1
docker rmi registry.aliyuncs.com/google_containers/kube-controller-manager:v1.21.1
docker rmi registry.aliyuncs.com/google_containers/kube-scheduler:v1.21.1
docker rmi registry.aliyuncs.com/google_containers/kube-proxy:v1.21.1
docker rmi registry.aliyuncs.com/google_containers/pause:3.4.1
docker rmi registry.aliyuncs.com/google_containers/etcd:3.4.13-0
docker rmi registry.aliyuncs.com/google_containers/coredns:1.8.0

master拉取镜像：
docker pull registry.aliyuncs.com/google_containers/kube-apiserver:v1.21.1&docker pull registry.aliyuncs.com/google_containers/kube-controller-manager:v1.21.1&docker pull registry.aliyuncs.com/google_containers/kube-scheduler:v1.21.1&docker pull registry.aliyuncs.com/google_containers/kube-proxy:v1.21.1&docker pull registry.aliyuncs.com/google_containers/pause:3.4.1&docker pull registry.aliyuncs.com/google_containers/etcd:3.4.13-0&docker pull registry.aliyuncs.com/google_containers/coredns:1.8.0

修改标签：
docker tag registry.aliyuncs.com/google_containers/kube-apiserver:v1.21.1 k8s.gcr.io/kube-apiserver:v1.21.1&docker tag registry.aliyuncs.com/google_containers/kube-controller-manager:v1.21.1 k8s.gcr.io/kube-controller-manager:v1.21.1&docker tag registry.aliyuncs.com/google_containers/kube-scheduler:v1.21.1 k8s.gcr.io/kube-scheduler:v1.21.1&docker tag registry.aliyuncs.com/google_containers/kube-proxy:v1.21.1 k8s.gcr.io/kube-proxy:v1.21.1&docker tag registry.aliyuncs.com/google_containers/pause:3.4.1 k8s.gcr.io/pause:3.4.1&docker tag registry.aliyuncs.com/google_containers/etcd:3.4.13-0 k8s.gcr.io/etcd:3.4.13-0&docker tag registry.aliyuncs.com/google_containers/coredns:1.8.0 k8s.gcr.io/coredns/coredns:v1.8.0

删除历史镜像：
docker rmi registry.aliyuncs.com/google_containers/kube-apiserver:v1.21.1&docker rmi registry.aliyuncs.com/google_containers/kube-controller-manager:v1.21.1&docker rmi registry.aliyuncs.com/google_containers/kube-scheduler:v1.21.1&docker rmi registry.aliyuncs.com/google_containers/kube-proxy:v1.21.1&docker rmi registry.aliyuncs.com/google_containers/pause:3.4.1&docker rmi registry.aliyuncs.com/google_containers/etcd:3.4.13-0&docker rmi registry.aliyuncs.com/google_containers/coredns:1.8.0

node需要拉取的镜像：
docker pull registry.aliyuncs.com/google_containers/kube-proxy:v1.21.1
docker pull registry.aliyuncs.com/google_containers/pause:3.4.1
修改标签：
docker tag registry.aliyuncs.com/google_containers/kube-proxy:v1.21.1 k8s.gcr.io/kube-proxy:v1.21.1
docker tag registry.aliyuncs.com/google_containers/pause:3.4.1 k8s.gcr.io/pause:3.4.1
删除历史镜像：
docker rmi registry.aliyuncs.com/google_containers/kube-proxy:v1.21.1
docker rmi registry.aliyuncs.com/google_containers/pause:3.4.1

7、master初始化：
kubeadm init或者
kubeadm init --kubernetes-version=v1.21.1 --apiserver-advertise-address 10.10.0.128 --pod-network-cidr=10.244.0.0/16 --service-cidr=10.1.0.0/16

根据上一步的提示执行如下
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id-u):$(id -g) $HOME/.kube/config

kubectl get nodes可以看到master还是处于NotReady状态

8、安装网络flannel组件
wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
kubectl apply -f kube-flannel.yml

9、k8s-node1和k8s-node2加入集群
kubeadm join 10.20.10.235:6443 --token xxxxxxxxxxxxxxxxxxxx
–discovery-token-ca-cert-hash sha256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(token是主节点初始化kubeadm init完成时的提示）加入集群

kubectl get pods -n kube-system
kubectl get nodes

如pod和node状态均正常，则搭建完成。