Difference between revisions of "Kubectl get nodes -o yaml"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{lc}} | {{lc}} | ||
| − | + | ||
| + | kubectl get nodes -o yaml | ||
| + | kubectl get nodes -o yaml -A | ||
| + | |||
| + | |||
| Line 18: | Line 22: | ||
* <code>eks.amazonaws.com/capacityType: ON_DEMAND</code> | * <code>eks.amazonaws.com/capacityType: ON_DEMAND</code> | ||
* <code>[[kubectl get pods -o yaml]] -A</code> | * <code>[[kubectl get pods -o yaml]] -A</code> | ||
| + | * <code>[[kubectl get nodes]]</code> | ||
| + | |||
== See also == | == See also == | ||
Revision as of 10:21, 3 January 2023
kubectl get nodes -o yaml kubectl get nodes -o yaml -A
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 -Akubectl get nodes
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:
