Difference between revisions of "PLEG is not healthy"
Jump to navigation
Jump to search
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | message: 'PLEG is not healthy: pleg was last seen active 3m14.617083429s ago; | + | message: '[[PLEG]] [[is not healthy]]: pleg was last seen active 3m14.617083429s ago; |
| − | + | * [[Pod Lifecycle Event Generator (PLEG)]] | |
| + | == Related == | ||
| + | * <code>[[NodeNotReady]]</code> | ||
* [[Pod Lifecycle Event Generator (PLEG)]] | * [[Pod Lifecycle Event Generator (PLEG)]] | ||
| − | + | * [[The kubelet on the node ip-123.123.123.123 is not healthy]] | |
| − | |||
| + | == See also == | ||
| + | * {{Kubelet}} | ||
| − | + | [[Category:K8s]] | |
Latest revision as of 15:16, 23 January 2024
message: 'PLEG is not healthy: pleg was last seen active 3m14.617083429s ago;
Related[edit]
NodeNotReady- Pod Lifecycle Event Generator (PLEG)
- The kubelet on the node ip-123.123.123.123 is not healthy
See also[edit]
kubelet, Pod Lifecycle Event Generator (PLEG), Kubelet conditions,/etc/kubernetes/kubelet.conf, /var/log/kubelet.log, Kubelet Container Runtime Interface (CRI),crictl,context deadline exceeded, E1122, E1124, Starting kubelet, NodeHasDiskPressure, NodeHasInsufficientMemory, rebooted, Node-pressure Eviction, Kubelet logs,manager: kubelet
Advertising:
