Difference between revisions of "Didn't match Pod's node affinity/selector"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
| + | == See also == | ||
| + | * {{FailedScheduling}} | ||
* {{Kubernetes selectors}} | * {{Kubernetes selectors}} | ||
* {{K8s affinity}} | * {{K8s affinity}} | ||
| + | |||
| + | [[Category:K8s]] | ||
Latest revision as of 16:17, 12 December 2023
0/2 nodes are available: 1 Too many pods, 1 nodes(s) didn't match Pod's node affinity/selector
0/24 nodes are available: 0/24 nodes are available: 1 node(s) didn't match pod anti-affinity rules, 1 node(s) were unschedulable, 2 node(s) had taint {node.kubernetes.io/not-ready}, that the pod did not tolerate, 20 node(s) didn't match Pod's node affinity/selector.
See also[edit]
- FailedScheduling:
Insufficient cpu,Insufficient memory,timed out waiting for the condition,unbound immediate PersistentVolumeClaims - Kubernetes selectors,
PodSelector:, labelSelector:, spec.selector - Kubernetes pod affinity and anti affinity, Kubernetes Node Affinity,
default-scheduler, affinity:, NodeAffinity, spec.affinity.podAntiAffinity
Advertising:
