1
2
3
4

10.10.10.166 master01-dev
10.10.10.167 master02-dev
10.10.10.168 master03-dev
10.10.10.169 vip.kube.dev

1
2
3
4
5
6
7
8
9

cat <<EOF | sudo tee /etc/modules-load.d/k8s.conf
br_netfilter
EOF

cat <<EOF | sudo tee /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
sudo sysctl --system

1
2
3
4
5

sysctl -w net.ipv4.ip_nonlocal_bind=1
echo net.ipv4.ip_nonlocal_bind=1 >> /etc/sysctl.conf

#check
sysctl net.ipv4.ip_nonlocal_bind

1
2
3

vim /etc/fstab 註解 swap.img
swapoff -a && sysctl -w vm.swappiness=0
reboot

1
2
3
4
5
6
7
8
9

sudo apt-mark unhold kubeadm kubectl kubelet

sudo apt-get install kubelet=1.22.8-00 kubeadm=1.22.8-00 kubectl=1.22.8-00

sudo apt-mark hold kubeadm kubectl kubelet

## If there is an network issud, just download the binary file and install
https://dl.k8s.io/v1.22.9/bin/linux/386/kubectl
sudo install -o root -g root -m 0755 kubectl /usr/bin/kubectl

1
2
3
4

# 執行前，記得修改 create-cluster-config.sh 參數
chmod +x create-cluster-config.sh
vim create-cluster-config.sh
./create-cluster-config.sh

1
2

kubeadm init --config kubeadm-configs.yaml --upload-certs --v=5
# Save the output!!

 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

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

Alternatively, if you are the root user, you can run:

  export KUBECONFIG=/etc/kubernetes/admin.conf

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/

You can now join any number of the control-plane node running the following command on each as root:

  kubeadm join 10.10.10.169:6443 --token qjfsuw.4ovqhe65b2lx59u2 \
        --discovery-token-ca-cert-hash sha256:8c28a32531adc4589fc885c24031a8c94e511f44e00caeffbd7c88e49bfff140 \
        --control-plane --certificate-key c0eb9d99e77f3c8f0994cb32b16f30ccc9c6f34e2f9836e1cc7d7d709281ac72

Please note that the certificate-key gives access to cluster sensitive data, keep it secret!
As a safeguard, uploaded-certs will be deleted in two hours; If necessary, you can use
"kubeadm init phase upload-certs --upload-certs" to reload certs afterward.

Then you can join any number of worker nodes by running the following on each as root:

kubeadm join 10.10.10.169:6443 --token qjfsuw.4ovqhe65b2lx59u2 \
        --discovery-token-ca-cert-hash sha256:8c28a32531adc4589fc885c24031a8c94e511f44e00caeffbd7c88e49bfff140

1

kubectl apply -f calico-v3.22.2.yaml

1
2
3

kubeadm join 10.10.10.169:6443 --token skev5a.tjtivikwvgrc7qur \
        --discovery-token-ca-cert-hash sha256:d4fd9a01c79f5d1cad2833cb4fbd026af376aa6bd0649cb4421029d456d86c17 \
        --control-plane --certificate-key 7d6ad10d2995e55063ad3493f34e5f6192bf45746ded783888576fcf3610be29 --v=7

1

kubectl taint nodes --all [node-role.kubernetes.io/master-](http://node-role.kubernetes.io/master-)