Rook Deployment failed due to networkPlugin

Placeboy commented 2 years ago

Hey, I'm having some trouble here. I typed commands below: kubectl create -f crds.yaml -f common.yaml -f operator.yaml

And my pod is always in the status: "ContainerCreating"

When I describe this pod, I got this:

Name:           rook-ceph-operator-75dd789779-j2t5h
Namespace:      rook-ceph
Priority:       0
Node:           k8s-node-1/10.211.55.123
Start Time:     Fri, 11 Feb 2022 19:02:51 +0800
Labels:         app=rook-ceph-operator
                pod-template-hash=75dd789779
Annotations:    <none>
Status:         Pending
IP:
IPs:            <none>
Controlled By:  ReplicaSet/rook-ceph-operator-75dd789779
Containers:
  rook-ceph-operator:
    Container ID:
    Image:         rook/ceph:master
    Image ID:
    Port:          9443/TCP
    Host Port:     0/TCP
    Args:
      ceph
      operator
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Environment:
      ROOK_CURRENT_NAMESPACE_ONLY:               false
      ROOK_DISCOVER_DEVICES_INTERVAL:            60m
      ROOK_HOSTPATH_REQUIRES_PRIVILEGED:         false
      ROOK_ENABLE_SELINUX_RELABELING:            true
      ROOK_ENABLE_FSGROUP:                       true
      ROOK_DISABLE_DEVICE_HOTPLUG:               false
      DISCOVER_DAEMON_UDEV_BLACKLIST:            (?i)dm-[0-9]+,(?i)rbd[0-9]+,(?i)nbd[0-9]+
      ROOK_UNREACHABLE_NODE_TOLERATION_SECONDS:  5
      NODE_NAME:                                  (v1:spec.nodeName)
      POD_NAME:                                  rook-ceph-operator-75dd789779-j2t5h (v1:metadata.name)
      POD_NAMESPACE:                             rook-ceph (v1:metadata.namespace)
    Mounts:
      /etc/ceph from default-config-dir (rw)
      /etc/webhook from webhook-cert (rw)
      /var/lib/rook from rook-config (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-d485m (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  rook-config:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  default-config-dir:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  webhook-cert:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  kube-api-access-d485m:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason                  Age                  From               Message
  ----     ------                  ----                 ----               -------
  Normal   Scheduled               17m                  default-scheduler  Successfully assigned rook-ceph/rook-ceph-operator-75dd789779-j2t5h to k8s-node-1
  Warning  FailedCreatePodSandBox  13m                  kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "3c00819be71e81e97394241dccc321ce893633d7c4e95c353b03013fe44561fc" network for pod "rook-ceph-operator-75dd789779-j2t5h": networkPlugin cni failed to set up pod "rook-ceph-operator-75dd789779-j2t5h_rook-ceph" network: netplugin failed with no error message: signal: killed
  Warning  FailedCreatePodSandBox  10m                  kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "1203bf2e1dd696f3e71464489202210d85ed8082af12bb30be2b1de37e29e6ab" network for pod "rook-ceph-operator-75dd789779-j2t5h": networkPlugin cni failed to set up pod "rook-ceph-operator-75dd789779-j2t5h_rook-ceph" network: netplugin failed with no error message: signal: killed
  Warning  FailedCreatePodSandBox  6m24s                kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "2492697793fe528e2ea75fe3342adbc22ea41ac317debc3cd42ce877262e7004" network for pod "rook-ceph-operator-75dd789779-j2t5h": networkPlugin cni failed to set up pod "rook-ceph-operator-75dd789779-j2t5h_rook-ceph" network: netplugin failed with no error message: signal: killed
  Warning  FailedCreatePodSandBox  2m43s                kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "9d557fb99172c28162a9289aaa25dd249e011b4aed13b87d7e80829f556e846e" network for pod "rook-ceph-operator-75dd789779-j2t5h": networkPlugin cni failed to set up pod "rook-ceph-operator-75dd789779-j2t5h_rook-ceph" network: netplugin failed with no error message: signal: killed
  Normal   SandboxChanged          2m41s (x4 over 13m)  kubelet            Pod sandbox changed, it will be killed and re-created.

It seems that there is something wrong with my cni.However, my weave is "Running":

Ah, and this is my k8s cluster:

It really bothers me.Could you tell me how to fix this?Thank you.

mmerrill3 commented 2 years ago

doesn't look like weave works with 1.23, see the kops update: https://github.com/kubernetes/kops/pull/12941

mmerrill3 commented 2 years ago

I know this project is not supported, but to support the CNI change in 1.23, something like this would need to get done:

https://github.com/weaveworks/weave/commit/c3c28ea27e5fda4220e65fd1d02e23a67a04c610

Jeansen commented 2 years ago

Yes, weave seems not to be working since 1.23 any longer. I've switched over to Flannel. That worked for me.

weaveworks / weave

Rook Deployment failed due to networkPlugin #3935