root@rke2-master1:~# vim /etc/rancher/rke2/config.yaml
token: 34798219
tls-san:
- 172.24.151.110 #vip
node-name: rke2-master1
node-taint:
- “CriticalAddonsOnly=true:NoExecute”
data-dir: /data/rke2
system-default-registry: “registry.cn-hangzhou.aliyuncs.com”
kube-proxy-arg:
- –proxy-mode=ipvs
- –ipvs-strict-arp=true
root@rke2-master1:~# kubectl get pod -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system cloud-controller-manager-rke2-master1 1/1 Running 0 29m
kube-system cloud-controller-manager-rke2-master2 1/1 Running 0 103m
kube-system cloud-controller-manager-rke2-master3 1/1 Running 0 98m
kube-system etcd-rke2-master1 1/1 Running 0 30m
kube-system etcd-rke2-master2 1/1 Running 0 103m
kube-system etcd-rke2-master3 1/1 Running 0 98m
kube-system helm-install-rke2-canal-hxpvk 0/1 Completed 0 29m
kube-system helm-install-rke2-coredns-l4th7 0/1 Completed 0 29m
kube-system helm-install-rke2-ingress-nginx-jxwr6 0/1 CrashLoopBackOff 10 (3m33s ago) 29m
kube-system helm-install-rke2-metrics-server-tfs8v 0/1 CrashLoopBackOff 10 (3m22s ago) 29m
kube-system helm-install-rke2-runtimeclasses-mvzqv 0/1 CrashLoopBackOff 10 (3m26s ago) 29m
kube-system helm-install-rke2-snapshot-controller-2lcrr 0/1 CrashLoopBackOff 10 (3m30s ago) 29m
kube-system helm-install-rke2-snapshot-controller-crd-h8fh5 0/1 CrashLoopBackOff 10 (3m27s ago) 29m
kube-system kube-apiserver-rke2-master1 1/1 Running 1 (30m ago) 30m
kube-system kube-apiserver-rke2-master2 1/1 Running 0 103m
kube-system kube-apiserver-rke2-master3 1/1 Running 0 98m
kube-system kube-controller-manager-rke2-master1 1/1 Running 0 29m
kube-system kube-controller-manager-rke2-master2 1/1 Running 0 103m
kube-system kube-controller-manager-rke2-master3 1/1 Running 0 98m
kube-system kube-proxy-rke2-master1 1/1 Running 0 30m
kube-system kube-proxy-rke2-master2 1/1 Running 0 103m
kube-system kube-proxy-rke2-master3 1/1 Running 0 98m
kube-system kube-proxy-rke2-node1 1/1 Running 0 77m
kube-system kube-scheduler-rke2-master1 1/1 Running 0 29m
kube-system kube-scheduler-rke2-master2 1/1 Running 0 103m
kube-system kube-scheduler-rke2-master3 1/1 Running 0 98m
kube-system rke2-canal-8vhhm 2/2 Running 0 29m
kube-system rke2-canal-hjcl9 2/2 Running 0 29m
kube-system rke2-canal-mzfcd 2/2 Running 0 29m
kube-system rke2-canal-rmfmp 2/2 Running 0 29m
kube-system rke2-coredns-rke2-coredns-74d7986b4f-r2g4w 0/1 Running 0 29m
kube-system rke2-coredns-rke2-coredns-autoscaler-5d56465b85-sc9h5 1/1 Running 11 (4s ago) 29m
Events:
Type Reason Age From Message
Normal Scheduled 32m default-scheduler Successfully assigned kube-system/helm-install-rke2-ingress-nginx-jxwr6 to rke2-node1
Normal Started 16m (x9 over 32m) kubelet Started container helm
Normal Created 11m (x10 over 32m) kubelet Created container: helm
Warning BackOff 2m28s (x139 over 32m) kubelet Back-off restarting failed container helm in pod helm-install-rke2-ingress-nginx-jxwr6_kube-system(8ebc46e8-8acd-4414-9432-eb2abd021eaf)
Normal Pulled 92s (x12 over 32m) kubelet Container image “registry.cn-hangzhou.aliyuncs.com/rancher/klipper-helm:v0.9.14-build20260309” already present on machine
我应该怎么处理，coredns 也没有正常允许起来