ip-10-0-12-9 is NotReady
Kubelet stopped reporting 14 minutes ago. 11 pods are Pending on it.
prod-eu-west-1
AWS · eu-west-1 · Kubernetes v1.31.2
$ kubectl get nodes -o wide
Nodes ready
7 / 8
Apps healthy
6 / 17
Pods running
102
15 not running · CPU 47% · Mem 64%
Services
11
1 load balancers · 5 ingress
Cluster CPU
00:0006:0012:0018:00now
Pods by phase
117 pods
Running 87% Pending 10% Failed 1% Succeeded 2%
Node capacity workers
Apps needing attention
Recent warnings
| Reason | Object | Message | Age |
|---|---|---|---|
WarningNodeNotReady | node/ip-10-0-12-9 | Node ip-10-0-12-9 status is now: NodeNotReady | 14m |
WarningFailedScheduling | pod/checkout-api-7d4f9c6b8-qx8k2 | 0/8 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/unreachable}, 3 node(s) had untolerated taint {node-role.kubernetes.io/control-plane}, 4 Insufficient memory. | 9m |
WarningMemoryPressure | node/ip-10-0-8-3 | Node ip-10-0-8-3 status is now: NodeHasInsufficientMemory | 26m |
WarningBackOff | pod/search-indexer-9a1e3f7c2-mn4 | Back-off restarting failed container search-indexer in pod search-indexer-9a1e3f7c2-mn4 | 31m |
WarningBackoffLimitExceeded | job/nightly-reconcile-28812960 | Job has reached the specified backoff limit | 5h |