Difference between revisions of "Kubectl get nodes -o yaml"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
| + | reason: [[KubeletReady]] | ||
reason: [[FilesystemIsNotReadOnly]] | reason: [[FilesystemIsNotReadOnly]] | ||
reason: [[KernelHasNoDeadlock]] | reason: [[KernelHasNoDeadlock]] | ||
| Line 10: | Line 11: | ||
reason: [[KubeletHasSufficientMemory]] | reason: [[KubeletHasSufficientMemory]] | ||
reason: [[KubeletHasSufficientPID]] | reason: [[KubeletHasSufficientPID]] | ||
| − | |||
reason: [[NoCorruptDockerOverlay2]] | reason: [[NoCorruptDockerOverlay2]] | ||
Revision as of 17:21, 13 December 2022
kubectl get nodes
reason: KubeletReady reason: FilesystemIsNotReadOnly reason: KernelHasNoDeadlock reason: KubeletHasNoDiskPressure reason: KubeletHasSufficientMemory reason: KubeletHasSufficientPID reason: NoCorruptDockerOverlay2
Related
- AWS EC2 instances:
r6i.xlarge, m6i.2xlarge eks.amazonaws.com/capacityType: ON_DEMANDkubectl get pods -o yaml -A
See also
- Kubectl information commands:
cluster-info|view|pods|nodes|services|version|describe | logs - 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:
