Kubernetes
Pod Scheduling Affinity Validator
Paste affinity or topologySpreadConstraints YAML to validate structure, operator syntax, and detect configurations that can never be satisfied.
No data is transmitted — everything runs locallyTool
About this tool
Pod Scheduling Affinity Validator
The Pod Scheduling Affinity Validator checks affinity, anti-affinity, and topologySpreadConstraints YAML for structural correctness and detects unsatisfiable scheduling constraints.
• Validate pod anti-affinity before deploying a high-availability workload
• Check topologySpreadConstraints syntax before applying to production
• Detect required affinity rules that no available node can satisfy
• Understand matchExpressions operator differences before writing a constraint
Affiliate disclosure
Developer-friendly cloud infrastructure. DigitalOcean provides cloud compute, networking, and managed databases with predictable pricing.
View Kubernetes options on DigitalOcean
External site · Independent provider · We may receive a commission · Not a recommendation
FAQ
What does this tool tell you?
The Pod Scheduling Affinity Validator checks affinity, anti-affinity, and topologySpreadConstraints YAML for structural correctness and detects unsatisfiable scheduling constraints.
What affects the result most?
nodeAffinity: requiredDuringSchedulingIgnoredDuringExecution vs preferredDuringScheduling. podAntiAffinity: topologyKey: kubernetes.io/hostname for pod spread across nodes. matchExpressions operators: In, NotIn, Exists, DoesNotExist — syntax and behavior.
How should I use the result?
Treat the tool's output as a first-pass check, not a proof of correctness. A clean pass means no issues in the patterns this tool recognizes; a failure points to a specific problem you can investigate in your source. The underlying spec is the authoritative source for edge cases.