2 nodes, one down

@afzaalahmadzeeshan

Name:               pool-cv01-001
Roles:              <none>
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/instance-type=s-1vcpu-2gb
                    beta.kubernetes.io/os=linux
                    doks.digitalocean.com/node-id=xxxxxx
                    doks.digitalocean.com/node-pool=pool-cv01
                    doks.digitalocean.com/node-pool-id=xxxxxx
                    doks.digitalocean.com/version=1.16.6-do.2
                    failure-domain.beta.kubernetes.io/region=ams3
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=pool-cv01-001
                    kubernetes.io/os=linux
                    region=ams3
Annotations:        alpha.kubernetes.io/provided-node-ip: 10.133.122.235
                    csi.volume.kubernetes.io/nodeid: {"dobs.csi.digitalocean.com":"185901933"}
                    io.cilium.network.ipv4-cilium-host: 10.244.0.205
                    io.cilium.network.ipv4-health-ip: 10.244.0.168
                    io.cilium.network.ipv4-pod-cidr: 10.244.0.128/25
                    node.alpha.kubernetes.io/ttl: 0
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Mon, 23 Mar 2020 16:33:50 +0100
Taints:             <none>
Unschedulable:      false
Conditions:
  Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----                 ------  -----------------                 ------------------                ------                       -------
  NetworkUnavailable   False   Tue, 24 Mar 2020 10:04:22 +0100   Tue, 24 Mar 2020 10:04:22 +0100   CiliumIsUp                   Cilium is running on this node
  MemoryPressure       False   Wed, 25 Mar 2020 08:08:23 +0100   Tue, 24 Mar 2020 10:03:40 +0100   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure         False   Wed, 25 Mar 2020 08:08:23 +0100   Tue, 24 Mar 2020 10:03:40 +0100   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure          False   Wed, 25 Mar 2020 08:08:23 +0100   Tue, 24 Mar 2020 10:03:40 +0100   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready                True    Wed, 25 Mar 2020 08:08:23 +0100   Tue, 24 Mar 2020 10:03:40 +0100   KubeletReady                 kubelet is posting ready status
Addresses:
  Hostname:    pool-cv01-001
  InternalIP:  xxx.xxx.xxx.xxx
  ExternalIP:  xxx.xxx.xxx.xxx
Capacity:
 cpu:                1
 ephemeral-storage:  51572172Ki
 hugepages-1Gi:      0
 hugepages-2Mi:      0
 memory:             2043372Ki
 pods:               110
Allocatable:
 cpu:                1
 ephemeral-storage:  xxxxxx
 hugepages-1Gi:      0
 hugepages-2Mi:      0
 memory:             1574Mi
 pods:               110
System Info:
 Machine ID:                 xxxxxx
 System UUID:                xxxxx
 Boot ID:                    xxxxx
 Kernel Version:             4.19.0-0.bpo.6-amd64
 OS Image:                   Debian GNU/Linux 9 (stretch)
 Operating System:           linux
 Architecture:               amd64
 Container Runtime Version:  docker://18.9.2
 Kubelet Version:            v1.16.6
 Kube-Proxy Version:         v1.16.6
PodCIDR:                     xxxxx
ProviderID:                  digitalocean://xxxxx
Non-terminated Pods:         (11 in total)
  Namespace                  Name                               CPU Requests  CPU Limits  Memory Requests  Memory Limits  AGE
  ---------                  ----                               ------------  ----------  ---------------  -------------  ---
  cattle-system              cattle-node-agent-lggqw            0 (0%)        0 (0%)      0 (0%)           0 (0%)         39h
  default                    lectuur-api-7dc69c5d-548s2         0 (0%)        0 (0%)      0 (0%)           0 (0%)         8h
  default                    lectuur-gui-757c846cbd-st57b       0 (0%)        0 (0%)      0 (0%)           0 (0%)         22h
  default                    lectuur-mongo-5c5d4d97cc-stzpl     0 (0%)        0 (0%)      0 (0%)           0 (0%)         8h
  kube-system                cilium-2dlzv                       300m (30%)    0 (0%)      300Mi (19%)      0 (0%)         39h
  kube-system                cilium-operator-d5cd7d758-5w5j8    0 (0%)        0 (0%)      0 (0%)           0 (0%)         39h
  kube-system                coredns-84c79f5fb4-zl9kd           100m (10%)    0 (0%)      70Mi (4%)        170Mi (10%)    39h
  kube-system                csi-do-controller-0                0 (0%)        0 (0%)      0 (0%)           0 (0%)         17h
  kube-system                csi-do-node-rpm47                  0 (0%)        0 (0%)      0 (0%)           0 (0%)         17h
  kube-system                do-node-agent-d62rw                102m (10%)    102m (10%)  80Mi (5%)        100Mi (6%)     39h
  kube-system                kube-proxy-9ffsk                   0 (0%)        0 (0%)      125Mi (7%)       0 (0%)         39h
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests     Limits
  --------           --------     ------
  cpu                502m (50%)   102m (10%)
  memory             575Mi (36%)  270Mi (17%)
  ephemeral-storage  0 (0%)       0 (0%)
Events:              <none>

What do I need to do to fix this?

Check the logs for the node and share what it says.

$ kubectl describe node <node-name>

This will tell you what is wrong with the node, and you can then get a solution for a specific problem with the node.