n8n not working

Viewed 16

My n8n pod cannot start due to "volume node affinity conflict"
using openebs-vg-lvm local storage.

PVC:
vn-homenv-nodevn-vn-n8n-n8n-mduefacv-0

Namespace:
ns-7amiquwa

The volume is tied to a node with taint:
database.run.claw.cloud/node

Please recover the pod by either:

  1. bringing back the original node where the local volume exists, or
  2. cloning/migrating this PVC to a network storage class
    so the pod can be scheduled on another node.

This is production data and I need the workflows inside.

0 Answers