操作系统centos7就可以了，由于是参考官方安装，兼容性不做考虑，系统配置都是虚拟机，能大点就最好，最小安装2C4G单台，酌情看着配置，磁盘存储放NFS就好了，能大点最好
| 操作系统 | 作用 | 配置 | 硬盘 |
|---|---|---|---|
| centos 7 | master | 4C8G | 50G |
| centos 7 | node1 | 4C16G | 50G |
| centos 7 | node2 | 4C16G | 50G |
| centos 7 | nfs | 2C4G | 200G |
准备工作
- 每个主机必须安装有部署docker
- 一些可以用来在主机间复制文件的基础设施。例如
ssh和scp就可以满足需求
安装k8s
修改hosts文件
以下步骤master和node都需要执行一边操作
cat <<EOF | tee /etc/hosts
192.168.170.128 master
192.168.170.129 node1
192.168.170.130 node2
192.168.170.131 nfs
EOF
echo "export KUBECONFIG=/etc/kubernetes/admin.conf" >> /etc/profile
source /etc/profile
打开内置的桥功能，这个是借助于iptables来实现的
echo "1" >/proc/sys/net/bridge/bridge-nf-call-iptables
cat <<EOF | tee /etc/modules-load.d/k8s.conf
br_netfilter
EOF
cat <<EOF | tee /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
sysctl --system
关闭swap
swapoff -a && sysctl -w vm.swappiness=0
sed -i '/swap/d' /etc/fstab
systemctl disable firewalld && systemctl stop firewalld
sed -i 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/selinux/config
setenforce 0
启用ipvs
modprobe -- ip_vs
modprobe -- ip_vs_rr
modprobe -- ip_vs_wrr
modprobe -- ip_vs_sh
modprobe -- nf_conntrack_ipv4
创建yum源
阿里云K8s源
cat <<EOF | tee /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
华为K8s源
cat <<EOF > /etc/yum.repos.d/kubernetes.repo
[kubernetes]
name=Kubernetes
baseurl=https://repo.huaweicloud.com/kubernetes/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://repo.huaweicloud.com/kubernetes/yum/doc/yum-key.gpg https://repo.huaweicloud.com/kubernetes/yum/doc/rpm-package-key.gpg
EOF
腾讯K8s源
cat <<EOF > /etc/yum.repos.d/kubernetes.repo
[kubernetes]
name=Kubernetes
baseurl=https://mirrors.cloud.tencent.com/kubernetes/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=0
EOF
清华大学K8s源
cat <<EOF > /etc/yum.repos.d/kubernetes.repo
[kubernetes]
name=kubernetes
baseurl=https://mirrors.tuna.tsinghua.edu.cn/kubernetes/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=0
EOF
安装服务
yum install -y kubelet kubeadm kubectl
systemctl enable --now kubelet
安装指定版本,参考docker
[root@node1 ~]# yum list kubeadm.x86_64 kubelet.x86_64 kubectl.x86_64 --showduplicates | sort -r |grep 1.20
kubelet.x86_64 1.20.2-0 kubernetes
kubelet.x86_64 1.20.2-0 @kubernetes
kubelet.x86_64 1.20.1-0 kubernetes
kubelet.x86_64 1.20.0-0 kubernetes
kubectl.x86_64 1.20.2-0 kubernetes
kubectl.x86_64 1.20.2-0 @kubernetes
kubectl.x86_64 1.20.1-0 kubernetes
kubectl.x86_64 1.20.0-0 kubernetes
kubeadm.x86_64 1.20.2-0 kubernetes
kubeadm.x86_64 1.20.2-0 @kubernetes
kubeadm.x86_64 1.20.1-0 kubernetes
kubeadm.x86_64 1.20.0-0 kubernetes
......
yum -y install kubelet-1.20.2-0 kubectl-1.20.2-0 kubeadm-1.20.2-0
导出配置文件
以下操作只在master上执行
kubeadm config print init-defaults --component-configs KubeletConfiguration > kubeadm.yaml
vim kubeadm.yaml
修改配置文件
我这边是直接修改好了的，直接粘贴就可以用了,如果有私有仓库的话，就把
imageRepository改成私有仓库地址，如：192.0.0.131/k8s
cat <<EOF | tee kubeadm.yaml
apiVersion: kubeadm.k8s.io/v1beta2
bootstrapTokens:
- groups:
- system:bootstrappers:kubeadm:default-node-token
token: abcdef.0123456789abcdef
ttl: 24h0m0s
usages:
- signing
- authentication
kind: InitConfiguration
localAPIEndpoint:
advertiseAddress: 192.168.170.128
bindPort: 6443
nodeRegistration:
criSocket: /var/run/dockershim.sock
name: master
taints:
- effect: NoSchedule
key: node-role.kubernetes.io/master
---
apiServer:
timeoutForControlPlane: 4m0s
apiVersion: kubeadm.k8s.io/v1beta2
certificatesDir: /etc/kubernetes/pki
clusterName: kubernetes
controllerManager: {}
dns:
type: CoreDNS
etcd:
local:
dataDir: /var/lib/etcd
imageRepository: daocloud.io/daocloud
kind: ClusterConfiguration
kubernetesVersion: v1.20.2
networking:
dnsDomain: cluster.local
serviceSubnet: 10.96.0.0/12
scheduler: {}
EOF
镜像拉取
kubeadm config images pull --config kubeadm.yaml
初始化
方法一
kubeadm init --config=kubeadm.yaml --upload-certs | tee kubeadm-init.log
方法二
kubeadm init --apiserver-advertise-address=192.168.170.128 --image-repository registry.aliyuncs.com/google_containers --kubernetes-version v1.20.1 --service-cidr=10.0.0.0/16 --pod-network-cidr=10.244.0.0/16
初始化完成后
[root@master kubernetes]# kubeadm init --apiserver-advertise-address=192.168.170.128 --image-repository registry.aliyuncs.com/google_containers --kubernetes-version v1.20.1 --service-cidr=10.0.0.0/16 --pod-network-cidr=10.244.0.0/16
[init] Using Kubernetes version: v1.20.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'
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local master] and IPs [10.0.0.1 192.168.170.128]
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [localhost master] and IPs [192.168.170.128 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [localhost master] and IPs [192.168.170.128 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[apiclient] All control plane components are healthy after 7.502782 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.20" in namespace kube-system with the configuration for the kubelets in the cluster
[upload-certs] Skipping phase. Please see --upload-certs
[mark-control-plane] Marking the node master as control-plane by adding the labels "node-role.kubernetes.io/master=''" and "node-role.kubernetes.io/control-plane='' (deprecated)"
[mark-control-plane] Marking the node master as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
[bootstrap-token] Using token: xlbbdb.bmmy2jnmb3ck9gbg
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to get nodes
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstrap-token] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstrap-token] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
[kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key
[addons] Applied essential addon: CoreDNS
[addons] Applied essential addon: kube-proxy
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
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/
Then you can join any number of worker nodes by running the following on each as root:
kubeadm join 192.168.170.128:6443 --token xlbbdb.bmmy2jnmb3ck9gbg \
--discovery-token-ca-cert-hash sha256:21d6ce5cb6f4ee321b14be6ae231ecb24d6980f5ece1dcc36c5b41c898dcc7f5
这条输出用于node加入master集群
kubeadm join 192.168.170.128:6443 --token xlbbdb.bmmy2jnmb3ck9gbg \
--discovery-token-ca-cert-hash sha256:21d6ce5cb6f4ee321b14be6ae231ecb24d6980f5ece1dcc36c5b41c898dcc7f5
初始化后操作
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
export KUBECONFIG=/etc/kubernetes/admin.conf
查看POD
[root@master kubernetes]# kubectl get pod -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-7f89b7bc75-26fgs 0/1 Pending 0 8m14s
kube-system coredns-7f89b7bc75-lqrdx 0/1 Pending 0 8m14s
kube-system etcd-master 1/1 Running 0 8m27s
kube-system kube-apiserver-master 1/1 Running 0 8m27s
kube-system kube-controller-manager-master 1/1 Running 0 8m27s
kube-system kube-proxy-gsxl9 1/1 Running 0 8m14s
kube-system kube-scheduler-master 1/1 Running 0 8m27s
这时候就k8s集群已经部署完成了，
coredns pending状态需要安装网络插件
k8s补全
yum install -y epel-release bash-completion
source /usr/share/bash-completion/bash_completion
source <(kubectl completion bash)
echo "source <(kubectl completion bash)" >> ~/.bashrc
或者
yum install -y epel-release bash-completion
cp /usr/share/bash-completion/completions/docker /etc/bash_completion.d/
systemctl enable --now docker
集群卸载
kubeadm reset
在node上执行操作
- 获取admin.conf文件
scp master:/etc/kubernetes/admin.conf /etc/kubernetes/
- 执行命令
[root@node1 ~]# kubeadm join 192.168.170.128:6443 --token xlbbdb.bmmy2jnmb3ck9gbg --discovery-token-ca-cert-hash sha256:21d6ce5cb6f4ee321b14be6ae231ecb24d6980f5ece1dcc36c5b41c898dcc7f5
[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.
- 获取node
[root@node1 ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
master Ready control-plane,master 22h v1.20.2
node1 Ready <none> 34s v1.20.2
