¶à´Î×°K8S¼¯ÈººóÕûÀíµÄÒ»¼ü°²×°½Å±¾¼°ÅäÖÃ˵Ã÷

#!/bin/bash


echo "1¡¢ÐÞ¸ÄDNSÅäÖÃÈçÓÐÐèÒª"
chattr -i /etc/resolv.conf
cat <<EOF >>  /etc/resolv.conf 
nameserver 10.139.0.246
nameserver 10.139.0.247
EOF


echo "ÇåÀíһЩÎÞÓõÄyum repos"
mkdir -p  /etc/yum.repos.d/back && mv /etc/yum.repos.d/ambari*   /etc/yum.repos.d/hdp*   /etc/yum.repos.d/back 

yum clean all

### ¹Ø±Õswap·ÖÇø
echo "swapoff ## ÁÙʱÉúЧ"
swapoff -a

## ÓÀ¾ÃÉúЧ¿ÉÒԱ༭/etc/fstabÎļþ ×¢Ê͵ôswapÄÇÐÐ

echo "¹Ø±Õ·À»ðǽ"
systemctl stop firewalld
systemctl disable --now firewalld

echo "¹Ø±Õsselinux"
setenforce 0
sed -i 's/enforcing/disabled/' /etc/selinux/config



# Äں˿ªÆôIPv4ת·¢ÐèÒª¿ªÆôÏÂÃæµÄÄ£¿é
modprobe br_netfilter

cat > /etc/sysctl.d/k8s.conf <<EOF
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_forward = 1
EOF



echo "ÉèÖÃdockerµÄĿ¼ÈíÁ¬½Ó /var/lib/docker°Ñdocker´æ´¢ÉèÖõ½Êý¾ÝÅÌÉÏ"
mkdir -p /data1/docker 
ln -s /data1/docker  /var/lib



echo "°²×°docker ÒÀÀµ "
yum install yum-utils device-mapper-persistent-data lvm2 -y




### ÐÂÔö Docker ²Ö¿â¡£
 yum-config-manager \
 --add-repo \
 https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
 
yum clean all

## °²×° Docker CE.
yum update -y && yum install -y \
  containerd.io-1.2.13 \
  docker-ce-19.03.11 \
  docker-ce-cli-19.03.11



## ´´½¨ /etc/docker Ŀ¼¡£
mkdir /etc/docker



cat > /etc/docker/daemon.json <<EOF
{
  "exec-opts": ["native.cgroupdriver=systemd"],
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "100m"
  },
  "storage-driver": "overlay2",
  "storage-opts": [
    "overlay2.override_kernel_check=true"
  ],
  "registry-mirrors": [ "https://1nj0zren.mirror.aliyuncs.com", "https://docker.mirrors.ustc.edu.cn", "http://f1361db2.m.daocloud.io", "https://registry.docker-cn.com" ]
}
EOF

sleep 1


systemctl daemon-reload
systemctl restart docker
sudo systemctl enable docker   


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
exclude=kube*
EOF



yum install -y kubelet-1.19.3 kubeadm-1.19.3 kubectl-1.19.3 --disableexcludes=kubernetes

sleep 1

kubeadm version

systemctl enable kubelet
systemctl daemon-reload
systemctl restart kubelet

apiVersion: kubeadm.k8s.io/v1beta2
bootstrapTokens:
- groups:
  - system:bootstrappers:kubeadm:default-node-token
  token: abcdef.0123456789abcdef
  ttl: 24h0m0s
  usages:
  - signing
  - authentication
kind: InitConfiguration
localAPIEndpoint:
  # ´Ë´¦ÐèÒªÐÞ¸ÄΪmasterÖ÷½Úµã IP
  advertiseAddress:  10.132.24.99
  bindPort: 6443
nodeRegistration:
  criSocket: /var/run/dockershim.sock
  name: kubernetes-master
  taints:
  - effect: NoSchedule
    key: node-role.kubernetes.io/master
---
apiServer:
  timeoutForControlPlane: 4m0s
apiVersion: kubeadm.k8s.io/v1beta2
certificatesDir: /etc/kubernetes/pki
clusterName: kubernetes


# ¶àÖ÷½ÚµãÐèÒªÐÞ¸ÄÕâÀÐÞ¸ÄΪÖ÷½Úµãip


controlPlaneEndpoint: "10.136.17.12:6443"
controllerManager: {}
dns:
  type: CoreDNS
etcd:
  local:
    dataDir: /var/lib/etcd
    
# ¹úÄÚ²»ÄÜ·ÃÎÊ Google£¬ÐÞ¸ÄΪ°¢ÀïÔÆ
imageRepository: registry.aliyuncs.com/google_containers
kind: ClusterConfiguration
# Ð޸İ汾ºÅ
kubernetesVersion: v1.19.0
networking:
  dnsDomain: cluster.local
  # ÅäÖÃ³É Calico µÄĬÈÏÍø¶Î
  podSubnet: "10.244.0.0/16"
  serviceSubnet: 10.1.0.0/16
scheduler: {}
---
# ¿ªÆô IPVS ģʽ

 apiVersion: kubeproxy.config.k8s.io/v1alpha1
kind: KubeProxyConfiguration
featureGates:
  SupportIPVSProxyMode: true
mode: ipvs

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

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.136.17.12:6443 --token abcdef.0123456789abcdef \
    --discovery-token-ca-cert-hash sha256:2fbacdf6a9473d5da1d98900f73cd4e2396521772b12ac99017d6ae756d8c3cc \
    --control-plane --certificate-key f0725584c26c192xxxxx4dc5804a101ebc5d7b40257837eea0676d1972cca

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.136.17.12:6443 --token abcdef.0123456789abcdef \
    --discovery-token-ca-cert-hash sha256:2fbacdf6a9473d5da1d98900f7xxxsssss6ae756d8c3cc 

mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

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

kubeadm join 10.136.17.12:6443 --token abcdef.0123456789abcdef \
    --discovery-token-ca-cert-hash sha256:2fbacdf6a9473d5da1d98900f73cd4e2396521772b12ac99017d6ae756d8c3cc \
    --control-plane --certificate-key f0725584c26c192xxxxx4dc5804a101ebc5d7b40257837eea0676d1972cca

#!/bin/bash
kubeadm reset -f 
ifconfig cni0 down && ip link delete cni0
ifconfig flannel.1 down && ip link delete flannel.1
rm -rf /var/lib/cni/