Difference between revisions of "Node.kubernetes.io/unreachable"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
Type Reason Age From Message | Type Reason Age From Message | ||
---- ------ ---- ---- ------- | ---- ------ ---- ---- ------- | ||
| − | [[Warning FailedScheduling]] 24s (x4 over 3m25s) [[default-scheduler]] 0/2 nodes are available: 1 node(s) had taint | + | [[Warning FailedScheduling]] 24s (x4 over 3m25s) [[default-scheduler]] 0/2 nodes are available: 1 node(s) had [[taint]] |
{[[node.kubernetes.io/disk-pressure]]: }, that the pod didn't tolerate, 1 node(s) had [[volume node affinity conflict]]. | {[[node.kubernetes.io/disk-pressure]]: }, that the pod didn't tolerate, 1 node(s) had [[volume node affinity conflict]]. | ||
Latest revision as of 10:54, 13 November 2023
node.kubernetes.io/unreachable: Node is unreachable from the node controller. This corresponds to the NodeCondition Ready being "Unknown".
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 24s (x4 over 3m25s) default-scheduler 0/2 nodes are available: 1 node(s) had taint {node.kubernetes.io/disk-pressure: }, that the pod didn't tolerate, 1 node(s) had volume node affinity conflict.
See also[edit]
node.kubernetes.io: /instance-type, /unreachable, node.kubernetes.io/not-ready, /disk-pressure- Kubernetes nodes,
node.kubernetes.ioK8s Node controller (node-controller),MemoryPressure, DiskPressure, NodeHasDiskPressure, events, NodeNotReady, Node-pressure Eviction, RemovingNode, ProviderID,kubectl node-shell, kubectl describe nodes
Advertising:
