Difference between revisions of "Kubectl describe nodes (conditions:)"
Jump to navigation
Jump to search
| Line 49: | Line 49: | ||
* [[CKA]] [[Understand how resource limits can affect Pod scheduling]] | * [[CKA]] [[Understand how resource limits can affect Pod scheduling]] | ||
* <code>[[kubectl get nodes -o yaml]]</code> | * <code>[[kubectl get nodes -o yaml]]</code> | ||
| − | + | * [[manager:]] | |
| − | * [[kubelet conditions]] | + | * <code>[[kubelet conditions]]</code> |
| + | * [[The kubelet on the node ip-123.123.123.123 is not healthy]] | ||
== See also == | == See also == | ||
Revision as of 15:17, 23 January 2024
kubectl describe nodes .../...
Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- FrequentContainerdRestart False Tue, 01 Nov 2022 07:34:25 +0100 Mon, 31 Oct 2022 23:53:28 +0100 NoFrequentContainerdRestart containerd is functioning properly KernelDeadlock False Tue, 01 Nov 2022 07:34:25 +0100 Mon, 31 Oct 2022 23:53:28 +0100 KernelHasNoDeadlock kernel has no deadlock ReadonlyFilesystem False Tue, 01 Nov 2022 07:34:25 +0100 Mon, 31 Oct 2022 23:53:28 +0100 FilesystemIsNotReadOnly Filesystem is not read-only CorruptDockerOverlay2 False Tue, 01 Nov 2022 07:34:25 +0100 Mon, 31 Oct 2022 23:53:28 +0100 NoCorruptDockerOverlay2 docker overlay2 is functioning properly FrequentUnregisterNetDevice False Tue, 01 Nov 2022 07:34:25 +0100 Mon, 31 Oct 2022 23:53:28 +0100 NoFrequentUnregisterNetDevice node is functioning properly FrequentKubeletRestart False Tue, 01 Nov 2022 07:34:25 +0100 Mon, 31 Oct 2022 23:53:28 +0100 NoFrequentKubeletRestart kubelet is functioning properly FrequentDockerRestart False Tue, 01 Nov 2022 07:34:25 +0100 Mon, 31 Oct 2022 23:53:28 +0100 NoFrequentDockerRestart docker is functioning properly NetworkUnavailable False Mon, 31 Oct 2022 23:53:41 +0100 Mon, 31 Oct 2022 23:53:41 +0100 RouteCreated RouteController created a route MemoryPressure False Tue, 01 Nov 2022 07:32:16 +0100 Mon, 31 Oct 2022 23:53:25 +0100 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Tue, 01 Nov 2022 07:32:16 +0100 Mon, 31 Oct 2022 23:53:25 +0100 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Tue, 01 Nov 2022 07:32:16 +0100 Mon, 31 Oct 2022 23:53:25 +0100 KubeletHasSufficientPID kubelet has sufficient PID available Ready True Tue, 01 Nov 2022 07:32:16 +0100 Mon, 31 Oct 2022 23:53:28 +0100 KubeletReady kubelet is posting ready status.
Conditions: Type Status Reason ---- ------ ------ Available True MinimumReplicasAvailable Progressing True NewReplicaSetAvailable
conditions:
- type: Available
status: 'True'
lastUpdateTime: '2022-11-23T09:41:50Z'
lastTransitionTime: '2022-11-23T09:41:50Z'
reason: MinimumReplicasAvailable
message: Deployment has minimum availability.
Related
- kubelet is posting ready status. AppArmor enabled
- CKA Understand how resource limits can affect Pod scheduling
kubectl get nodes -o yaml- manager:
kubelet conditions- The kubelet on the node ip-123.123.123.123 is not healthy
See also
- Kubernetes events, Kubernetes node events:
[ Normal | Warning ],kubectl events, kubectl get events:BackOff,FailedMount, FailedAttachVolume, TaintManagerEviction, InvalidDiskCapacity,FailedScheduling, kubectl describe events, Unhealthy,conditions:, UpdatedLoadBalancer, BackoffLimitExceeded - K8s troubleshooting:
kubectl logs, kubectl top, kubectl get events -A, kubectl describe pod, Liveness, Readiness,Kubernetes events, Pulling image, OOMKilled, ProbeWarning, Reason,FailedScheduling,errImagePull, ImagePullBackOff, Kubelet conditions:MemoryPressure, DiskPressure, KubeletHasSufficientPID, KubeletReady, kubectl [ debug | attach | exec ] kubectl cluster-info dump, SimKube, KWOK
Advertising:
