Fix the “node affinity conflict” warning in Kubernetes by matching PersistentVolume and pod labels. Use kubectl commands and YAML edits to get deployment healthy.

Problem

You may see this warning when deploying a Node.js app to Kubernetes:

pgsql

1 node(s) had volume node affinity conflict

This happens when your PersistentVolume is bound to a node that doesn’t match the affinity rules of your pod or cluster. Your app won’t start or the pod will be in Pending or CrashLoopBackOff state.

Solution

1. Check Node Labels

Run kubectl get nodes –show-labels to see if the node has the required affinity label.

2. Match Volume Affinity

Run kubectl describe pv <volume-name> to see nodeAffinity settings. Make sure your pod spec or deployment matches this.

3. Fix by Relabeling or Updating Specs

  • Update node label with:
kubectl label node <node-name> disktype=ssd
  • Or, add a nodeSelector to your pod’s YAML.

Also Read: Impact Of Serverless On Node.js Development in 2025

4. Reapply & Redeploy

Apply and redeploy to rebind the volume correctly.

Conclusion

This is a mismatch in affinity between PV and pod. Fix it by checking node labels, editing YAML files and volume bindings.