离线安装过程，仅供参考，陆续更新。
机器三台
master 为01 slave 为03 04
以下步骤1到7，三台都需操作。
swapoff -a
sed -i s/SELINUX=enforcing/SELINUX=disabled/g /etc/selinux/config
setenforce 0
getenforce 确保为disabled
我是三台之前互相都做免密
执行sysctl --system生效配置文件
也可以参照其他人的操作（该图来源于https://www.jianshu.com/p/cccbed8e85da）
本地是通过代理yum安装
systemctl start docker
systemctl enable docker 设置开机自启动
systemctl restart docker
并查看docker info中的Cgroup的值，原来为
Cgroup Driver: cgroupfs 修改为systemd
本地也是通过代理安装kubeadm, kubelet, kubectl，版本需要一致，注意安装顺序，组件之间彼此存在依赖关系。
在安装过程中，由于内网环境缺少很多依赖，下图仅供参考。
在master上操作
查看需下载哪些镜像
是在外网搭建了docker环境，进行镜像拉取，然后在导入内网进行安装。
在master节点上执行kubeadm init命令。
（如果使用flannel网络。则要把参数中必须设置–pod-network-cidr=
10.244.0.0/16，这个IP地址是固定）
kubeadm init --kubernetes-version=v1.22.11
–apiserver-advertise-address=11.12.4.106
–pod-network-cidr=10.244.0.0/16
如果出现该界面，表示安装成功。然后执行图中三条语句（mkdir cp chown）。
最后一句为节点加入master时执行。
**在两台slave上安装了一些组件。**如 图。
复制图中语句kubeadm join 分别在两台slave中执行。
表示安装成功。执行master执行 kubectl get no查看三台状态。
三个节点都为not ready状态，因为网络组件还没安装。三台机器都需要安装插件。（cni-plugin可能是多安装了）。镜像也都是在外网下载好docker load 导入。
创建kube-flannel.yml，并执行。
kubectl apply -f kube-flannel.yml
如果更换yml文件，先执行kubectl delete -f kube-flannel.yml删除，然后再apply。（因为该文件耽误了诸多时间，截图该文件内容仅供参考。）
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
name: psp.flannel.unprivileged
annotations:
seccomp.security.alpha.kubernetes.io/allowedProfileNames: docker/default
seccomp.security.alpha.kubernetes.io/defaultProfileName: docker/default
apparmor.security.beta.kubernetes.io/allowedProfileNames: runtime/default
apparmor.security.beta.kubernetes.io/defaultProfileName: runtime/default
spec:
privileged: false
volumes:
- configMap
- secret
- emptyDir
- hostPath
allowedHostPaths:
- pathPrefix: "/etc/cni/net.d"
- pathPrefix: "/etc/kube-flannel"
- pathPrefix: "/run/flannel"
readOnlyRootFilesystem: false
# Users and groups
runAsUser:
rule: RunAsAny
supplementalGroups:
rule: RunAsAny
fsGroup:
rule: RunAsAny
# Privilege Escalation
allowPrivilegeEscalation: false
defaultAllowPrivilegeEscalation: false
# Capabilities
allowedCapabilities: ['NET_ADMIN', 'NET_RAW']
defaultAddCapabilities: []
requiredDropCapabilities: []
# Host namespaces
hostPID: false
hostIPC: false
hostNetwork: true
hostPorts:
- min: 0
max: 65535
# SELinux
seLinux:
# SELinux is unused in CaaSP
rule: 'RunAsAny'
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: flannel
rules:
- apiGroups: ['extensions']
resources: ['podsecuritypolicies']
verbs: ['use']
resourceNames: ['psp.flannel.unprivileged']
- apiGroups:
- ""
resources:
- pods
verbs:
- get
- apiGroups:
- ""
resources:
- nodes
verbs:
- list
- watch
- apiGroups:
- ""
resources:
- nodes/status
verbs:
- patch
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: flannel
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: flannel
subjects:
- kind: ServiceAccount
name: flannel
namespace: kube-system
---
apiVersion: v1
kind: ServiceAccount
metadata:
name: flannel
namespace: kube-system
---
kind: ConfigMap
apiVersion: v1
metadata:
name: kube-flannel-cfg
namespace: kube-system
labels:
tier: node
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",
"Backend": {
"Type": "vxlan"
}
}
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: kube-flannel-ds
namespace: kube-system
labels:
tier: node
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
image: k8s.gcr.io/flannel:v0.10.0-amd64
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: k8s.gcr.io/flannel:v0.10.0-amd64
command:
- /opt/bin/flanneld
args:
- --ip-masq
- --kube-subnet-mgr
resources:
requests:
cpu: "100m"
memory: "50Mi"
limits:
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
volumeMounts:
- name: run
mountPath: /run/flannel
- name: flannel-cfg
mountPath: /etc/kube-flannel/
volumes:
- name: run
hostPath:
path: /run/flannel
- name: cni
hostPath:
path: /etc/cni/net.d
- name: flannel-cfg
configMap:
name: kube-flannel-cfg
成功后，如图。
kubeadm config print init-defaults 显示kubeadm.yaml版本信息。
如果flannel等pod没起或报错，查看pod日志，网上基本都有解决办法。
1.在此次安装过程中，有通过删除相关错误容器，然后容器自启动会恢复
2. 有的在执行kubeadm init执行没加参数，–pod-network-cidr=
10.244.0.0/16。
