一、准备工作
1、准备三台资源不小于2CPU-2G内存-20G硬盘服务器(要求在同一个局域网)
2、服务器规划
主机名 | ip | CPU | 内存 | 硬盘 | 操作系统 |
---|---|---|---|---|---|
k8s-master | 192.168.204.10 | 2C | 2G | 20G | centos7 |
k8s-node1 | 192.168.204.11 | 2C | 2G | 20G | centos7 |
k8s-node2 | 192.168.204.12 | 2C | 2G | 20G | centos7 |
3、修改静态ip,防止ip变动(我使用的是虚拟机所以我的网卡名称是ifcfg-ens33)
vim /etc/sysconfig/network-scripts/ifcfg-ens33
BOOTPROTO="dhcp" #修改成BOOTPROTO="static"
ONBOOT="yes" #默认是yes,如果是no则改为"yes"
在配置文件的行尾添加一下配置
IPADDR=192.168.204.10 #网卡的IP地址
GATEWAY=192.168.204.2 #默认网关IP地址(虚拟机的默认网关都是xxx.xxx.xxx.2可以在虚拟网络编辑器里面查看不会的话百度)
NETMASK=255.255.255.0 #子网掩码
DNS1=114.114.114.114 #dns1服务器
DNS2=8.8.8.8 #dns2服务器
4、配置好静态IP后重启网卡设置
systemctl restart network
5、更换国内yum源
curl -o /etc/yum.repos.d/CentOS-Base.repo https://mirrors.aliyun.com/repo/Centos-7.repo
curl -o /etc/yum.repos.d/docker-ce.repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
二、初始化配置(master和node都执行)
1、修改主机名
hostnamectl set-hostname k8s-master && bash #k8s-master
hostnamectl set-hostname k8s-node1 && bash #k8s-node1
hostnamectl set-hostname k8s-node2 && bash #k8s-node2
2、主机名解析
cat >> /etc/hosts << EOF
192.168.204.10 k8s-master
192.168.204.11 k8s-node1
192.168.204.12 k8s-node2
EOF
3、配置iptables规则
iptables -F && iptables -P FORWARD ACCEPT
4、关闭防火墙、selinux、swap分区
systemctl disable firewalld && systemctl stop firewalld
sed -ri 's#(SELINUX=).*#\1disabled#' /etc/selinux/config
setenforce 0
swapoff -a
sed -i ' / swap / s/^\(.*\)$/#\1/g' /etc/fstab
5、修改系统的网络和内核参数
cat <<EOF > /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_forward=1
vm.max_map_count=262144
EOF
modprobe br_netfilter
sysctl -p /etc/sysctl.d/k8s.conf
6、清理 yum 软件包缓存并且重新建立缓存
yum clean all && yum makecache fast
三、安装docker(master和node都执行)
1、修改系统的网络参数
cat <<EOF > /etc/sysctl.d/docker.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_forward=1
EOF
sysctl -p /etc/sysctl.d/docker.conf
2、安装依赖
yum install -y yum-utils device-mapper-persistent-data lvm2 vim wget lrzsz net-tools
3、安装docker-ce
yum install -y docker-ce-20.10.24 docker-ce-cli-20.10.24 containerd.io
#需要安装docker20.10版本的,高于docker20.10版本的会影响后续k8s的部署
#如果之前安装过docker,可以使用yum remove docker-ce卸载
4、配置镜像加速和设置 Docker 的 cgroup 驱动程序为 systemd
mkdir -p /etc/docker
cat <<EOF > /etc/docker/daemon.json
{
"registry-mirrors": ["https://gwtzlfl6.mirror.aliyuncs.com"],
"exec-opts": ["native.cgroupdriver=systemd"]
}
EOF
5、启动docker并设置开机自启
systemctl enable --now docker
四、安装k8s集群
1、设置k8s阿里镜像源(master和node都执行)
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
2、安装kubeadm,kubeelet和kubectl(master和node都执行)
yum install -y kubelet-1.23.17-0 kubeadm-1.23.17-0 kubectl-1.23.17-0
systemctl enable --now kubelet
kubeadm version #查看kubeadm版本
3、将镜像手动拉取下来,这样在初始化的时候会更快一些(只在master执行)
kubeadm config images pull --image-repository registry.aliyuncs.com/google_containers
4、初始化 Kubernetes 集群(只在master执行)
kubeadm init \
--apiserver-advertise-address=192.168.204.10 \
--image-repository registry.aliyuncs.com/google_containers \
--kubernetes-version v1.23.17 \
--service-cidr=10.96.0.0/12 \
--pod-network-cidr=10.244.0.0/16 \
--ignore-preflight-errors=all
# –apiserver-advertise-address # 集群通告地址(master 机器IP,这里用的万兆网)
# –image-repository # 由于默认拉取镜像地址k8s.gcr.io国内无法访问,这里指定阿里云镜像仓库地址
# –kubernetes-version # K8s版本,与上面安装的一致
# –service-cidr # 集群内部虚拟网络,Pod统一访问入口,可以不用更改,直接用上面的参数
# –pod-network-cidr # Pod网络,与下面部署的CNI网络组件yaml中保持一致,可以不用更改,直接用上面的参数
5、初始化结果
①拷贝kubeconfig文件(只在master执行)
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
②添加node节点到集群中(只在node节点执行)!!!注意不要复制粘贴
kubeadm join 192.168.8.210:6443 --token abcdef.0123456789abcdef \
--discovery-token-ca-cert-hash sha256:cea8e2b170ffae49b1bc17e09f698f132a9a5e55a76715211ab9cb8cc703fec2
#注意不要复制粘贴,这里是你上面初始化成功之后输出的结果,是将node加入你的k8s集群
#如果不小心清理的你的token,可以使用kubeadm token list输出你的token信息
#或者重新生成一个新的token,kubeadm token create --print-join-command
五、安装网络插件Flannel (只在master执行)
1、先将(Flannel)网络插件pull到自己本地,如果该步骤执行失败或者无法拉取镜像,请参考下一步操作。该镜像由大喵桑丶-CSDN博客提供参考文章:https://blog.csdn.net/qq_35700085/article/details/140950872
docker pull registry.cn-hangzhou.aliyuncs.com/liuk8s/flannel:v0.21.5
docker pull registry.cn-hangzhou.aliyuncs.com/liuk8s/flannel-cni-plugin:v1.1.2
2、!!!Flannel网络插件备用方案 先将(Flannel)网络插件通过百度网盘下载到自己本地
https://pan.baidu.com/s/1faZoKaY1ZmxiYJGLyzywog
提取码:98z8
下载好的文件有三个,flannel-cni-plugin_v1.1.2.tar,flannel_v0.21.5.tar,kube-flannel.yml
下载好docker镜像后上传到你的服务器中,执行以下操作:
docker load -i flannel_v0.21.5.tar
docker load -i flannel-cni-plugin_v1.1.2.tar
通过docker images 查看镜像发现镜像已成功导入,可以按步骤继续执行。
[root@aly ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
registry.cn-hangzhou.aliyuncs.com/liuk8s/flannel v0.21.5 a6c0cb5dbd21 16 months ago 68.9MB
registry.cn-hangzhou.aliyuncs.com/liuk8s/flannel-cni-plugin v1.1.2 7a2dcab94698 21 months ago 7.97MB
3、上传以下kube-flannel.yml文件到master节点,创建一个kube-flannel.yml文件粘贴进去即可
---
kind: Namespace
apiVersion: v1
metadata:
name: kube-flannel
labels:
k8s-app: flannel
pod-security.kubernetes.io/enforce: privileged
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
labels:
k8s-app: flannel
name: flannel
rules:
- apiGroups:
- ""
resources:
- pods
verbs:
- get
- apiGroups:
- ""
resources:
- nodes
verbs:
- get
- list
- watch
- apiGroups:
- ""
resources:
- nodes/status
verbs:
- patch
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
labels:
k8s-app: flannel
name: flannel
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: flannel
subjects:
- kind: ServiceAccount
name: flannel
namespace: kube-flannel
---
apiVersion: v1
kind: ServiceAccount
metadata:
labels:
k8s-app: flannel
name: flannel
namespace: kube-flannel
---
kind: ConfigMap
apiVersion: v1
metadata:
name: kube-flannel-cfg
namespace: kube-flannel
labels:
tier: node
k8s-app: flannel
app: flannel
data:
cni-conf.json: |
{
"name": "cbr0",
"cniVersion": "0.3.1",
"plugins": [
{
"type": "flannel",
"delegate": {
"hairpinMode": true,
"isDefaultGateway": true
}
},
{
"type": "portmap",
"capabilities": {
"portMappings": true
}
}
]
}
net-conf.json: |
{
"Network": "10.244.0.0/16",
"EnableNFTables": false,
"Backend": {
"Type": "vxlan"
}
}
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: kube-flannel-ds
namespace: kube-flannel
labels:
tier: node
app: flannel
k8s-app: flannel
spec:
selector:
matchLabels:
app: flannel
template:
metadata:
labels:
tier: node
app: flannel
spec:
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: kubernetes.io/os
operator: In
values:
- linux
hostNetwork: true
priorityClassName: system-node-critical
tolerations:
- operator: Exists
effect: NoSchedule
serviceAccountName: flannel
initContainers:
- name: install-cni-plugin
image: registry.cn-hangzhou.aliyuncs.com/liuk8s/flannel-cni-plugin:v1.1.2
command:
- cp
args:
- -f
- /flannel
- /opt/cni/bin/flannel
volumeMounts:
- name: cni-plugin
mountPath: /opt/cni/bin
- name: install-cni
image: registry.cn-hangzhou.aliyuncs.com/liuk8s/flannel:v0.21.5
command:
- cp
args:
- -f
- /etc/kube-flannel/cni-conf.json
- /etc/cni/net.d/10-flannel.conflist
volumeMounts:
- name: cni
mountPath: /etc/cni/net.d
- name: flannel-cfg
mountPath: /etc/kube-flannel/
containers:
- name: kube-flannel
image: registry.cn-hangzhou.aliyuncs.com/liuk8s/flannel:v0.21.5
command:
- /opt/bin/flanneld
args:
- --ip-masq
- --kube-subnet-mgr
resources:
requests:
cpu: "100m"
memory: "50Mi"
securityContext:
privileged: false
capabilities:
add: ["NET_ADMIN", "NET_RAW"]
env:
- name: POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: POD_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
- name: EVENT_QUEUE_DEPTH
value: "5000"
volumeMounts:
- name: run
mountPath: /run/flannel
- name: flannel-cfg
mountPath: /etc/kube-flannel/
- name: xtables-lock
mountPath: /run/xtables.lock
volumes:
- name: run
hostPath:
path: /run/flannel
- name: cni-plugin
hostPath:
path: /opt/cni/bin
- name: cni
hostPath:
path: /etc/cni/net.d
- name: flannel-cfg
configMap:
name: kube-flannel-cfg
- name: xtables-lock
hostPath:
path: /run/xtables.lock
type: FileOrCreate
4、安装Flannel(只在master节点执行)
kubectl apply -f kube-flannel.yml
5、过2分钟左右检查集群状态(只在master节点执行)
kubectl get node
如果看到三个节点的STATUS列都为Ready,那么恭喜你,安装成功
[root@k8s-master ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
k8s-master Ready control-plane,master 8m3s v1.23.17
k8s-node1 Ready <none> 7m34s v1.23.17
k8s-node2 Ready <none> 7m30s v1.23.17
六、配置kubectl补全
1、kubectl自动补全依赖 bash-completion 运行下面命令安装
yum -y install bash-completion
2、设置环境变量
echo "source /usr/share/bash-completion/bash_completion" >> ~/.bashrc
echo 'source <(kubectl completion bash)' >>~/.bashrc
source ~/.bashrc
3、检查是否有正常内容输出
type _init_completion