当前位置: 首页 > 知识库问答 >
问题:

无法识别“kube-flannel.yml”:与版本“extensions/v1beta1”中的种类“daemonset”不匹配

贾烨
2023-03-14

在k8s工作节点上:

admin1@poc-k8s-node1:~$sudo kubeadm join 192.168.137.2:6443-token s03usq.lrz343lolmrz00lf-discovery-token-ca-cert-hash sha256:5c6b88a78e7b303debda447fa6f7fb48e3746bedc07dc2a518fbc80d48f37ba4-ignore-preflight-errors=all

[preflight] Running pre-flight checks
        [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
        [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 19.03.5. Latest validated version: 18.09
        [WARNING Port-10250]: Port 10250 is in use
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[kubelet-start] Downloading configuration for the kubelet from the "kubelet-config-1.16" ConfigMap in the kube-system namespace
[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] Activating the kubelet service
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
[kubelet-check] Initial timeout of 40s passed.
error execution phase kubelet-start: error uploading crisocket: timed out waiting for the condition
To see the stack trace of this error execute with --v=5 or higher

admin1@poc-k8s-node1:~$journalctl-u kubelet-f

Nov 21 05:28:15 POC-k8s-node1 kubelet[55491]: E1121 05:28:15.784713   55491 reflector.go:123] k8s.io/kubernetes/pkg/kubelet/kubelet.go:459: Failed to list *v1.Node: Unauthorized
Nov 21 05:28:15 POC-k8s-node1 kubelet[55491]: E1121 05:28:15.827982   55491 kubelet.go:2267] node "poc-k8s-node1" not found
Nov 21 05:28:15 POC-k8s-node1 kubelet[55491]: E1121 05:28:15.928413   55491 kubelet.go:2267] node "poc-k8s-node1" not found
Nov 21 05:28:15 POC-k8s-node1 kubelet[55491]: E1121 05:28:15.988489   55491 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1beta1.RuntimeClass: Unauthorized
Nov 21 05:28:16 POC-k8s-node1 kubelet[55491]: E1121 05:28:16.029295   55491 kubelet.go:2267] node "poc-k8s-node1" not found
Nov 21 05:28:16 POC-k8s-node1 kubelet[55491]: E1121 05:28:16.129571   55491 kubelet.go:2267] node "poc-k8s-node1" not found
Nov 21 05:28:16 POC-k8s-node1 kubelet[55491]: E1121 05:28:16.187178   55491 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1beta1.CSIDriver: Unauthorized
Nov 21 05:28:16 POC-k8s-node1 kubelet[55491]: E1121 05:28:16.230227   55491 kubelet.go:2267] node "poc-k8s-node1" not found
Nov 21 05:28:16 POC-k8s-node1 kubelet[55491]: E1121 05:28:16.330777   55491 kubelet.go:2267] node "poc-k8s-node1" not found
Nov 21 05:28:16 POC-k8s-node1 kubelet[55491]: E1121 05:28:16.386758   55491 reflector.go:123] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:46: Failed to list *v1.Pod: Unauthorized
Nov 21 05:28:16 POC-k8s-node1 kubelet[55491]: E1121 05:28:16.431420   55491 kubelet.go:2267] node "poc-k8s-node1" not found
Nov 21 06:30:45 POC-k8s-node1 kubelet[75467]: E1121 06:30:45.670520   75467 reflector.go:123] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:46: Failed to list *v1.Pod: Unauthorized
Nov 21 06:30:45 POC-k8s-node1 kubelet[75467]: E1121 06:30:45.691050   75467 kubelet.go:2267] node "poc-k8s-node1" not found
Nov 21 06:30:45 POC-k8s-node1 kubelet[75467]: E1121 06:30:45.791249   75467 kubelet.go:2267] node "poc-k8s-node1" not found
Nov 21 06:30:45 POC-k8s-node1 kubelet[75467]: E1121 06:30:45.866004

在K8s上Master:root@poc-k8s-master:~#kubeadm配置图像拉取

[config/images] Pulled k8s.gcr.io/kube-apiserver:v1.16.3
[config/images] Pulled k8s.gcr.io/kube-controller-manager:v1.16.3
[config/images] Pulled k8s.gcr.io/kube-scheduler:v1.16.3
[config/images] Pulled k8s.gcr.io/kube-proxy:v1.16.3
[config/images] Pulled k8s.gcr.io/pause:3.1
[config/images] Pulled k8s.gcr.io/etcd:3.3.15-0
[config/images] Pulled k8s.gcr.io/coredns:1.6.2
root@POC-k8s-master:~# export KUBECONFIG=/etc/kubernetes/admin.conf

root@poc-k8s-master:~#sysctl net.bridge.bridge-nf-call-iptables=1

net.bridge.bridge-nf-call-iptables = 1

root@poc-k8s-master:~#kubectl get pods--所有名称空间

NAMESPACE     NAME                                     READY   STATUS    RESTARTS   AGE
*****kube-system   coredns-5644d7b6d9-7xk42                 0/1     Pending   0          91s
kube-system   coredns-5644d7b6d9-mbrlx                 0/1     Pending   0          91s*****
kube-system   etcd-poc-k8s-master                      1/1     Running   0          51s
kube-system   kube-apiserver-poc-k8s-master            1/1     Running   0          32s
kube-system   kube-controller-manager-poc-k8s-master   1/1     Running   0          47s
kube-system   kube-proxy-xqb2d                         1/1     Running   0          91s
kube-system   kube-scheduler-poc-k8s-master            1/1     Running   0          38s

root@poc-k8s-master:~#kubectl apply-f

https://raw.githubusercontent.com/coreos/flannel/c5d10c8/Documentation/kube-flannel.yml
clusterrole.rbac.authorization.k8s.io/flannel created
clusterrolebinding.rbac.authorization.k8s.io/flannel created
serviceaccount/flannel created
configmap/kube-flannel-cfg created
unable to recognize "https://raw.githubusercontent.com/coreos/flannel/c5d10c8/Documentation/kube-flannel.yml": no matches for kind "DaemonSet" in version "extensions/v1beta1"
unable to recognize "https://raw.githubusercontent.com/coreos/flannel/c5d10c8/Documentation/kube-flannel.yml": no matches for kind "DaemonSet" in version "extensions/v1beta1"
unable to recognize "https://raw.githubusercontent.com/coreos/flannel/c5d10c8/Documentation/kube-flannel.yml": no matches for kind "DaemonSet" in version "extensions/v1beta1"
unable to recognize "https://raw.githubusercontent.com/coreos/flannel/c5d10c8/Documentathtml" target="_blank">ion/kube-flannel.yml": no matches for kind "DaemonSet" in version "extensions/v1beta1"
unable to recognize "https://raw.githubusercontent.com/coreos/flannel/c5d10c8/Documentation/kube-flannel.yml": no matches for kind "DaemonSet" in version "extensions/v1beta1"

共有1个答案

乐正意智
2023-03-14

您似乎使用的是k8s版本1.16,并且daemonset API组更改为apps/v1

更新以下链接:https://raw.githubusercontent.com/coreos/flannel/master/documentation/kube-flannel.yml

还有一个问题:https://github.com/kubernetes/website/issues/16441

 类似资料:
  • 我正在尝试在主节点上安装flannel,但出现以下错误。 无法识别“https://raw.githubusercontent.com/coreos/flannel/bc79dd1505b0c8681ece4de4c0d86c5cd2643275/Documentation/kube-flannel.yml:版本“extensions/v1beta1”中的种类“守护程序”没有匹配项 kubectl

  • 问题内容: 我正在尝试使用Jenkins在Kubernetes中部署下一个frontend-deployment.yaml,但是出现下一个错误: 如果我从Kubernetes集群中的机器上运行,则可以正常工作。 这是我的frontend-deployment.yaml: 问题答案: 我的问题是因为在Jenkinsfile中,我使用的是Kubernetes仪表板URL而不是Kubernetes AP

  • 路径:%JAVA_HOME\bin;%M2_HOME\bin;... java版本工作良好 java版本“1.8.0_45”java(TM)SE运行时环境(build1.8.0_45-B15)java HotSpot(TM)64位服务器VM(build25.45-B02,混合模式) “Mvn'n'est pas reconnu en tant que commande interne ou ext

  • 我使用Kubernetes官方文档中的yaml文件在Kubernetes中创建部署,它在顶部使用。然后键入创建此部署,但出现以下错误: 经过一些搜索,我将更改为,然后用yaml文件重新创建部署,结果运行良好。 所以,我想知道和之间有什么区别。它与库伯内特的版本有关吗?

  • 我一直使用Mac电脑,不记得以前遇到过这种情况,所以我不确定自己做错了什么。互联网上已经有一些问题了,但我还没有找到解决办法。 我刚买了一台新的mac电脑,我正在尝试使用rJava java--version java10.0.1 2018-04-17Java(TM)SE运行时环境18.3(构建10.0.1 10)JavaHotSpot(TM)64位服务器VM 18.3(构建10.0.1 10,混

  • 我想在共享托管服务器中安装php依赖项,但是作曲家说我的php版本是(对我的依赖项来说太旧了),这是真的,所以我用一个叫做"MultiPHP管理器”。好吧,直到我重试运行,作曲家一直说我的php版本是。 然后我在一个虚拟页面中检查了,它说我的版本是。我还运行了,结果显示我的版本是。 我试过了 重新加载 运行和但它说已禁用,但我使用名为“MultiHP INI编辑器”的cpanel工具启用了它,说已