Showing results for 
Search instead for 
Did you mean: 

Head's Up! Site migration is underway. Phase 2: migrate recent content

Kubernetes Node fails strategy



I wanted to know that,

I am using Neo4j 5.1 Enterprise edition on EKS with 3 core instance(core-1, core-2, core-3). Also, I use EBS CSI driver to dynamically create volume and use node auto-scaler. so when my one instance (core-1) failed then node auto-scaler create new node and in that node core-1 is ready to schedule again but it not able to start because of failed node and newly created nodes AZ are different and in dynamically generated PV AZ is a node selector so that's why its give a error.

So there is any way to when any instance fail then its automatic up and bind with old volume without giving any node failure strategy