Difference between revisions of "Kubernetes Nodes"
Jump to navigation
Jump to search
↑ https://kubernetes.io/docs/concepts/architecture/nodes/#condition
| Line 10: | Line 10: | ||
== Node conditions <ref>https://kubernetes.io/docs/concepts/architecture/nodes/#condition</ref> == | == Node conditions <ref>https://kubernetes.io/docs/concepts/architecture/nodes/#condition</ref> == | ||
| − | + | * [[Ready]] | |
| − | + | * [[DiskPressure]] | |
| − | + | * [[MemoryPressure]] | |
| − | + | * [[PIDPressure]] | |
| − | + | * [[NetworkUnavailable]] | |
Related: <code>[[SchedulingDisabled]]</code> | Related: <code>[[SchedulingDisabled]]</code> | ||
Revision as of 13:51, 9 December 2022
Kubernetes Nodes or working nodes.
https://kubernetes.io/docs/concepts/architecture/nodes/
kubectl get nodeskubectl describe nodeskubectl label nodeskubectl uncordonkubectl taint nodeskubectl drain
Node conditions [1]
Related: SchedulingDisabled
Related
- CKA v1.23: Understand host networking configuration on the cluster nodes
Pod The node had condition:- Container: is approaching memory limit
- cordoned Node
See also
- 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 - Kubernetes monitoring, node conditions, Kube-state-metrics (KSM), Prometheus, VictoriaMetrics,
node-problem-detector, Thanos, log collection,ProbeWarning, Kubernetes node-problem-detector, Pixie, OpenMetrics,kind: PodMonitor, Jaeger
Advertising:
