I am receiving the following error when I do <div class="highlight highlight-sourc

Chapter 8 about kubernetes-in-action HOT 2 OPEN

luksa commented on June 22, 2024

Chapter 8

from kubernetes-in-action.

Comments (2)

taylorturner commented on June 22, 2024 1

In the closed issues someone recommended removing the cpu and memory config from the pod yaml. It worked for me.
#17

from kubernetes-in-action.

guanlinz commented on June 22, 2024

I was using EKS on AWS to deploy the downward-env pod, there were several errors poped up.

It shows some thing wrong with the CNI

Events:
  Type     Reason                  Age   From               Message
  ----     ------                  ----  ----               -------
  Normal   Scheduled               6s    default-scheduler  Successfully assigned default/downward to ip-172-31-14-144.cn-north-1.compute.internal
  Warning  FailedCreatePodSandBox  0s    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "865e1d36f580b219c9d4aa21b7fb4d9875132a45666aaa8cf0042c6b615715be" network for pod "downward": networkPlugin cni failed to set up pod "downward_default" network: CNI failed to retrieve network namespace path: cannot find network namespace for the terminated container "865e1d36f580b219c9d4aa21b7fb4d9875132a45666aaa8cf0042c6b615715be"

I thought there must be something wrong with my pod specification file, so I copied directly from the github, but got some memory too low error shows in 2)

Kubernets still complains about the pod memory too low

Minimum memory limit allowed is 6MB

So I modified the memory limit parameter in the pod specification file, it fixed the issue for me.

spec:
  containers:
  - name: main
    image: busybox
    command: ["sleep", "9999999"]
    resources:
      requests:
        cpu: 15m
        memory: 60Mi
      limits:
        cpu: 100m
        memory: 60Mi

from kubernetes-in-action.

Recommend Projects