Difference between revisions of "Kubectl get nodes -o yaml"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 8: | Line 8: | ||
| − | + | === Reasons === | |
reason: [[KubeletReady]] | reason: [[KubeletReady]] | ||
reason: [[FilesystemIsNotReadOnly]] | reason: [[FilesystemIsNotReadOnly]] | ||
| Line 24: | Line 24: | ||
* <code>[[kubectl get nodes]]</code> | * <code>[[kubectl get nodes]]</code> | ||
* <code>[[conditions:]]</code> | * <code>[[conditions:]]</code> | ||
| + | * <code>[[[[annotations:]]</code> | ||
== See also == | == See also == | ||
Latest revision as of 14:33, 3 January 2023
kubectl get nodes -o yaml kubectl get nodes -o yaml -A
annotations:
Reasons[edit]
reason: KubeletReady reason: FilesystemIsNotReadOnly reason: KernelHasNoDeadlock reason: KubeletHasNoDiskPressure reason: KubeletHasSufficientMemory reason: KubeletHasSufficientPID reason: NoCorruptDockerOverlay2
Related[edit]
- AWS EC2 instances:
r6i.xlarge, m6i.2xlarge eks.amazonaws.com/capacityType: ON_DEMANDkubectl get pods -o yaml -Akubectl get nodesconditions:[[annotations:
See also[edit]
- 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:
