[BUG] runtime network not ready: NetworkReady=false reason:NetworkPluginNotRead

已于 2022-11-27 23:51:40 修改
阅读量7.4k 收藏 8
点赞数
分类专栏： bug 文章标签： bug kubernetes docker flannel kube-systen
于 2022-11-27 23:49:21 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/keyuchen_01/article/details/128070052
版权
当执行kubectl get node发现节点状态为NotReady，原因是flannel网络插件未正常初始化。解决方法包括下载kube-flannel.yaml文件，检查镜像版本，更新配置以启用CIDR分配，并确保kubelet服务重启。注意不同环境可能需要对应版本的flannel镜像。
摘要由CSDN通过智能技术生成

1 背景

执行kubectl get node是发现节点是NotReady状态，接着执行kubectl describe node 节点名 详细查看NotReady状态原因如下：

runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized

在这里插入图片描述

2 解决思路

2.1 获取kube-flannel.yaml文件

首先flannel没有正常初始化，由于没有正确获取到kube-flannel.yaml文件。可以通过如下链接下载该yaml文件

wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml

这里由于该网站被禁止，所有不能正常下载，提供如下kube-flannel.yaml源文件

---
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']
  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/v1beta1
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/v1beta1
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-amd64
  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
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - amd64
      hostNetwork: true
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.12.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: quay.io/coreos/flannel:v0.12.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"]
        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
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-arm64
  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
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - arm64
      hostNetwork: true
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.12.0-arm64
        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: quay.io/coreos/flannel:v0.12.0-arm64
        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"]
        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
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-arm
  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
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - arm
      hostNetwork: true
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.12.0-arm
        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: quay.io/coreos/flannel:v0.12.0-arm
        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"]
        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
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-ppc64le
  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
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - ppc64le
      hostNetwork: true
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.12.0-ppc64le
        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: quay.io/coreos/flannel:v0.12.0-ppc64le
        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"]
        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
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-s390x
  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
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - s390x
      hostNetwork: true
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.12.0-s390x
        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: quay.io/coreos/flannel:v0.12.0-s390x
        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"]
        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

2.2 注意事项

注意：
1 这里的镜像和你当前环境中的镜像是否一致，如果不一致则会在部署flannel的Pod时重新下载镜像。
2 如果你的环境中已存在flannel的镜像，则修改yaml文件为当前环境中的镜像版本即可
在这里插入图片描述
3 如果镜像版本不一致，则需要重新下载，下载会比较慢，建议从github下载再导入

docker load < flanneld-v0.12.0-amd64.docker

在这里插入图片描述

2.3 安装flannel的pod

kubectl apply -f kube-flannel.yaml

如果执行后仍报错且flannel的pod再反反复复创建
在这里插入图片描述
通过查看pod的日志，可以发现报错如下：

kubectl logs kube-flannel-ds-amd64-mdthz -n kube-system

在这里插入图片描述
解决方案：

vim /etc/kubernetes/manifests/kube-controller-manager.yaml

添加如下内容：

--allocate-node-cidrs=true
--cluster-cidr=10.244.0.0/16

在这里插入图片描述
注：这里的10.244.0.0/16为kube-flannel.yaml中自带的ip，按要求修改即可
修改完成之后，重启kubelet服务后，发现flannel正常。
在这里插入图片描述

不以物喜2020
关注
专栏目录
Rancher入门到精通-2.0 Runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:
隔壁老瓦的专栏
10-11 1万+
Runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized 1 Runtime network not ready: Ne...
Rancher实践：运行时网络未就绪——网络插件未准备就绪
TechProX的博客
08-15 614
本文将重点讨论在启动Rancher时出现的运行时网络未就绪错误，并提供解决方案和相应的源代码示例。在本文中，我们讨论了Rancher中运行时网络未准备就绪的问题，并提供了相应的解决方案和源代码示例。通过检查网络插件的状态、确认配置文件和选项、检查依赖项和日志，以及重启网络插件，我们可以解决这个问题并使Rancher正常运行。确保与Rancher关联的网络插件（通常是calico或flannel）的Pod正在运行，并且没有出现任何错误。要解决这个问题，我们需要确保正确配置和准备Rancher的网络插件。
node节点join失败错误信息：K8S container runtime network not ready cni plugin not initialized
最新发布
还想做MAD
08-09 327
K8S network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized
“Container runtime network not ready“ networkReady=“NetworkReady=false reason:NetworkPluginNotReady
weixin_70661795的博客
02-28 5485
k8s集群初始化后， node3节点加入集群， 状态Noready。2、查看node3节点kubelet状态，以及日志。3、复制cni到问题节点。原因：缺少网络cni。
KubeletNotReady runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:d
Less Is More
08-14 2343
mkdir -p /etc/cni/net.d vi 10-flannel.conflist { "name": "cbr0", "plugins": [ { "type": "flannel", "delegate": { "hairpinMode": true, "isDefaultGateway": true } }, { "type": "portmap", "ca..
network is not ready: runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady me
风水道人
12-17 853
换个kube2-flannel.yml 版本直接使用就可以。
KubeletNotReady runtime network not ready: NetworkReady=false reason:NetworkPluginNotRe...
dianjiejian4745的博客
05-02 1万+
1. mkdir -p /etc/cni/net.d 2. vi 10-flannel.conflist { "name": "cbr0", "plugins": [ { "type": "flannel", "delegate": { "hairpinMode": true, "isDefaultGateway": tru...
00 kubeadm简易安装
weixin_43960970的博客
05-20 289
shttps://last2win.com/2020/01/30/k8s-install-and-use-and-fix-bug/ https://segmentfault.com/a/1190000037682150 前言-为什么是k8s v1.16.0？ 最新版的v1.16.2试过了，一直无法安装完成，安装到kubeadm init那一步执行后，报了很多错，如：node xxx not found等。centos7都重装了几次，还是无法解决。用了一天都没安装完，差点放弃。后来在网上搜到的安装教程基本都是
A002-185-2537-翁格婉（个人期末作业）
qq_33680482的博客
01-02 3445
Excel查找结合项目主题说明1.作业查词说明1.1第一次查词1.1.1Requirements baseline（需求基线）1.1.2Enterprise Architect（企业架构师）1.1.3Unified Modeling Language（ 统一建模语言）1.1.3Unified Modeling Language（ 统一建模语言）1.1.5Asynchronous Processes（异步进程）1.1.6association class（关联类）1.1.7behavioral model a
高通开发系列 - linux kernel内核升级msm-3.18升至msm-4.9(1)
fulinux的博客
02-10 1870
高通开发系列 - linux kernel更新msm-3.18升至msm-4.9
【docker】安装redis和mysql生产实战
阿杰
11-23 461
docker安装诸如redis，mysql等程序非常方便，但是如果不是为了学习，生产环境的部署还是要注意很多问题的 redis 拉取镜像 创建映射目录 修改配置文件官网： https://github.com/redis/redis/blob/6.0.16/redis.conf下载对应本版的配置文件redis/redis.conf at 6.0.16 · redis/redis · GitHub（单独复制redis.conf或则将整个源码拉下来） 然后将配置文件放在上面创建的 /usr/docker/t
[ElasticSearch]ElasticSearch,Kibana安装与启动
SmartSi
10-16 1644
1. 检查JDK版本使用如下命令检验JDK版本：xiaosi@Qunar:~$ java -version java version "1.7.0_40" Java(TM) SE Runtime Environment (build 1.7.0_40-b43) Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode) xiaosi
kubelet Container runtime network not ready“ networkReady=“NetworkReady=false reason:NetworkPluginNo
TH_NUM的博客
10-06 9900
Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin
Error排错：container runtime network not ready
热门推荐
m0_59267075的博客
11-10 2万+
container runtime network not ready network plugin is not ready: cni config uninitialized
Rancher - 运行时网络未准备就绪：NetworkReady=false 原因：NetworkPluginNotReady 信息：编程
DevRevolt的博客
09-09 414
通过上述步骤，我们可以确保Rancher的网络插件配置正确，运行状态正常，并尝试重新初始化网络插件以解决"Rancher - 运行时网络未准备就绪：NetworkReady=false 原因：NetworkPluginNotReady 信息：编程"错误。如果配置和状态都正常，但仍然遇到网络插件未准备就绪的错误，那么可能是由于网络插件的初始化过程中遇到了一些问题。下面是一个简单的示例，展示了如何使用Python脚本检查并打印网络插件的配置信息。我们可以检查输出结果，确保网络插件的Pod正常运行。
《Kubernetes故障篇：Container runtime network not ready》
东城绝神
08-23 4561
1、环境信息如下： 2、报错信息如下： Warning FailedCreatePodSandBox 106s (x39 over 10m) kubelet (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create containerd task: failed to create shim task: OCI ru
NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni con
guoshaoliang789的专栏
12-10 8366
错误现象: untime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized 解决办法: docker pull quay.io/coreos/flannel:v0.9.1-amd64 mkdir -p /etc/cni/net.d/ cat <<EOF> /.
k8s node NotReady：NetworkReady=false reason:NetworkPluginNotReady；cni plugin not initialized
m0_55691056的博客
04-03 2630
kubectl获取node节点，集群状态检测时，master、node一直处于NotReady状态。NetworkReady=false reason:NetworkPluginNotReady；cni plugin not initialized
runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
06-03
这个错误通常是由于Kubernetes集群网络插件未正确安装或初始化而导致的。您需要检查您的集群网络插件是否正确安装，并且是否为每个节点正确配置了CNI插件。您可以使用kubectl命令检查网络插件的状态，例如通过运行以下命令来检查calico网络插件的状态： ``` kubectl get pods -n kube-system | grep calico ``` 如果您的网络插件没有成功启动，您可以尝试重新安装它或者查看其日志以了解更多详情。另外，您还可以检查您的节点是否正确配置了网络接口，并且是否具有正确的IP地址。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值