Pod Status waiting more than one day

Viewed 137

Event:

0/51 nodes are available: 1 Too many pods, 1 node(s) had untolerated taint {database.run.claw.cloud/node: }, 16 node(s) had volume node affinity conflict, 18 Insufficient cpu, 2 node(s) had untolerated taint {monitor.run.claw.cloud/node: }, 3 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }, 4 node(s) had untolerated taint {node.cilium.io/agent-not-ready: }, 6 node(s) had untolerated taint {devbox.sealos.io/node: }. preemption: 0/51 nodes are available: 19 No preemption victims found for incoming pod, 32 Preemption is not helpful for scheduling..
2 Answers

Currently, the free availability zone resources are limited, and you may encounter issues creating or updating applications. It is recommended that you create applications in the paid availability zone. If you have data on your application that needs to be backed up, please contact us via email: [email protected].

I was four versions behind on n8n and hesitant to update. I went ahead without backing up my work, and now for the past two days I’ve been getting this error: “no healthy upstream.” What should I do? :'( :'(

Please send an email to [email protected] and provide your account ID and region, and we will assist you with troubleshooting.

I sent an email : Sat, Sep 20, 10:53 PM (2 days ago), no answer. I even paid for a year still not working.

to: [email protected]
date: Sep 20, 2025, 10:53 PM
subject: no healthy upstream
mailed-by: gmail.com