php做网站框架,怎么推广公司,东莞商城网站建设公司,响应式网页需要设计几张图最后编辑时间#xff1a;2024/3/26
适用于1.24之后的版本
单节点配置 检查是否已经安装kubectl, kubelet, kubeadm直接输入命令确定#xff0c;如果提示没有该指令则正确 kubectl
kubelet
kubeadm如果之前安装#xff0c;首先reset#xff0c;然后使用apt remove和snap r…最后编辑时间2024/3/26
适用于1.24之后的版本
单节点配置 检查是否已经安装kubectl, kubelet, kubeadm直接输入命令确定如果提示没有该指令则正确 kubectl
kubelet
kubeadm如果之前安装首先reset然后使用apt remove和snap remove删除 sudo kubeadm reset
sudo apt remove kubectl kubelet kubeadm
sudo snap remove kubectl kubelet kubeadm关闭防火墙 查看防火墙状态 inactive说明是未激活 sudo ufw status开机不启动防火墙重启即可生效 sudo ufw disable确保docker已经安装并正确配置cgroup管理器例如 配置docker sudo mkdir -p /etc/docker
sudo vi /etc/docker/daemon.json#{
# registry-mirrors: [https://2m9jza5s.mirror.aliyuncs.com],
# insecure-registries: [localhost:32000],
# exec-opts: [ native.cgroupdriversystemd ],
# data-root: /data/wzh/docker/image,
# default-runtime: nvidia,
# runtimes: {
# nvidia: {
# path: /usr/bin/nvidia-container-runtime,
# runtimeArgs: []
# }
# }
#}
{registry-mirrors: [https://2m9jza5s.mirror.aliyuncs.com], # 必要insecure-registries: [localhost:32000], exec-opts: [ native.cgroupdriversystemd ], # 必要data-root: /data/wzh/docker/image, # 配置镜像目录
}https://???.mirror.aliyuncs.com配成自己的见链接。 sudo systemctl restart docker安装cri-dockerd 以下内容适用1.24之后版本 进入https://github.com/Mirantis/cri-dockerd/releases 下载对应cri-dockerd 博主的机器为ubuntu-20因此下载cri-dockerd_0.3.12.3-0.ubuntu-focal_amd64.deb 然后适用apt安装注意选择当前目录./ sudo apt install ./cri-dockerd_0.3.12.3-0.ubuntu-focal_amd64.deb然后启用cri-dockerd sudo systemctl daemon-reload
sudo systemctl enable cri-docker.socket
sudo systemctl start cri-docker.socket cri-docker
cri-dockerd --version
ls -al /var/run/cri-dockerd.sock安装kubectl, kubelet, kubeadm # 检查这个kubernetes-cni
sudo apt install -y kubelet1.28.2-00 kubectl1.28.2-00 kubeadm1.28.2-00
# apt list kubernetes-cni -a可以查找有什么版本
# sudo journalctl -u kubelet # 查看kubelet状态
# systemctl status kubelet # 查看kubelet状态禁用swap sudo vi /etc/default/kubelet
# 添加下面这行
KUBELET_EXTRA_ARGS--fail-swap-onfalse
sudo systemctl daemon-reload
sudo systemctl restart kubeletsudo vi /etc/fstab
注释掉带 /swap.img的那行出错后首先重置 sudo kubeadm reset
rm -rf ~/.kube
sudo rm -rf /etc/cni/net.d配置dockerd sudo vi /etc/containerd/config.toml
#如果看到了这行
disabled_plugins : [cri]#将这行用#注释或者将cri删除
#disabled_plugins : [cri]disabled_plugins : []#重启容器运行时
sudo systemctl restart containerd配置镜像位置 停止cri-docker服务sudo systemctl stop cri-docker 编辑vi /usr/lib/systemd/system/cri-docker.service 找到ExecStart在最后添加–pod-infra-container-imageregistry.aliyuncs.com/google_containers/pause:3.9 ExecStart/usr/bin/cri-dockerd --container-runtime-endpoint fd:// --pod-infra-container-imageregistry.aliyuncs.com/google_containers/pause:3.9重新加载服务sudo systemctl daemon-reload 启动cri-docker服务sudo systemctl start cri-docker kubeadm初始化 sudo kubeadm init --kubernetes-versionv1.28.2 --apiserver-advertise-address0.0.0.0 --image-repository registry.aliyuncs.com/google_containers --ignore-preflight-errorsSwap --pod-network-cidr10.24.0.0/16 --cri-socket unix:///var/run/cri-dockerd.sock出错使用下述进行debug sudo journalctl -xeu kubeletinit成功后提示如下表示成功了 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/.kubesudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/configsudo chown $(id -u):$(id -g) $HOME/.kube/configAlternatively, if you are the root user, you can run:export KUBECONFIG/etc/kubernetes/admin.confYou 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 10.181.8.94:6443 --token 0desqq.a4oq0rwqyursqah9 \--discovery-token-ca-cert-hash sha256:7e181cd0f0a435adf7746b17b09b10dba5c9d83936e92fffdc1e67cbf4a9cc06配置登录选项 mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/configinit成功后检查kubectl $ kubectl get pod -A此时仍有两个没有打开
需要配置网络
创建文件flannel.yaml内容如下
---
kind: Namespace
apiVersion: v1
metadata:name: kube-flannellabels:k8s-app: flannelpod-security.kubernetes.io/enforce: privileged
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:labels:k8s-app: flannelname: flannel
rules:
- apiGroups:- resources:- podsverbs:- get
- apiGroups:- resources:- nodesverbs:- get- list- watch
- apiGroups:- resources:- nodes/statusverbs:- patch
- apiGroups:- networking.k8s.ioresources:- clustercidrsverbs:- list- watch
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:labels:k8s-app: flannelname: flannel
roleRef:apiGroup: rbac.authorization.k8s.iokind: ClusterRolename: flannel
subjects:
- kind: ServiceAccountname: flannelnamespace: kube-flannel
---
apiVersion: v1
kind: ServiceAccount
metadata:labels:k8s-app: flannelname: flannelnamespace: kube-flannel
---
kind: ConfigMap
apiVersion: v1
metadata:name: kube-flannel-cfgnamespace: kube-flannellabels:tier: nodek8s-app: flannelapp: 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-dsnamespace: kube-flannellabels:tier: nodeapp: flannelk8s-app: flannel
spec:selector:matchLabels:app: flanneltemplate:metadata:labels:tier: nodeapp: flannelspec:affinity:nodeAffinity:requiredDuringSchedulingIgnoredDuringExecution:nodeSelectorTerms:- matchExpressions:- key: kubernetes.io/osoperator: Invalues:- linuxhostNetwork: truepriorityClassName: system-node-criticaltolerations:- operator: Existseffect: NoScheduleserviceAccountName: flannelinitContainers:- name: install-cni-pluginimage: rancher/mirrored-flannelcni-flannel-cni-plugin:v1.0.0#image: docker.io/rancher/mirrored-flannelcni-flannel-cni-plugin:v1.1.2command:- cpargs:- -f- /flannel- /opt/cni/bin/flannelvolumeMounts:- name: cni-pluginmountPath: /opt/cni/bin- name: install-cniimage: lizhenliang/flannel:v0.11.0-amd64#image: docker.io/rancher/mirrored-flannelcni-flannel:v0.21.5command:- cpargs:- -f- /etc/kube-flannel/cni-conf.json- /etc/cni/net.d/10-flannel.conflistvolumeMounts:- name: cnimountPath: /etc/cni/net.d- name: flannel-cfgmountPath: /etc/kube-flannel/containers:- name: kube-flannelimage: lizhenliang/flannel:v0.11.0-amd64#image: docker.io/rancher/mirrored-flannelcni-flannel:v0.21.5command:- /opt/bin/flanneldargs:- --ip-masq- --kube-subnet-mgrresources:requests:cpu: 100mmemory: 50MisecurityContext:privileged: falsecapabilities:add: [NET_ADMIN, NET_RAW]env:- name: POD_NAMEvalueFrom:fieldRef:fieldPath: metadata.name- name: POD_NAMESPACEvalueFrom:fieldRef:fieldPath: metadata.namespace- name: EVENT_QUEUE_DEPTHvalue: 5000volumeMounts:- name: runmountPath: /run/flannel- name: flannel-cfgmountPath: /etc/kube-flannel/- name: xtables-lockmountPath: /run/xtables.lockvolumes:- name: runhostPath:path: /run/flannel- name: cni-pluginhostPath:path: /opt/cni/bin- name: cnihostPath:path: /etc/cni/net.d- name: flannel-cfgconfigMap:name: kube-flannel-cfg- name: xtables-lockhostPath:path: /run/xtables.locktype: FileOrCreate创建完成后执行kubectl apply -f flannel.yaml执行很快但是需要等待一会才会启动一会会出现
wzhchen:~$ kubectl get pod -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-flannel kube-flannel-ds-xqpqb 1/1 Running 0 11h
kube-system coredns-7f6cbbb7b8-w5lp8 1/1 Running 0 12h
kube-system coredns-7f6cbbb7b8-xmps6 1/1 Running 0 12h
kube-system etcd-chen 1/1 Running 0 12h
kube-system kube-apiserver-chen 1/1 Running 0 12h
kube-system kube-controller-manager-chen 1/1 Running 0 12h
kube-system kube-proxy-c5tks 1/1 Running 0 12h
kube-system kube-scheduler-chen 1/1 Running 0 12h
wzhchen:~$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
chen Ready control-plane,master 13h v1.28.2现在master可以在去除所有污点后执行(“:…” - “-” )以下未去除污点操作可以使用kubectl describe进行查看是否有污点
$ kubectl taint nodes --all node-role.kubernetes.io/master-
$ kubectl taint nodes --all foo-
