How to schedule replicas and persistent volume in different availability zones about mongodb-kubernetes-operator HOT 6 CLOSED

Hey, you can pass on spec.statefulSet.spec.template.spec.affinity.podAntiAffinity in the mongodb resource, or even topologySpreadConstraints.

from mongodb-kubernetes-operator.

But after a POD restart, The POD schedules on az1 but its persistent volume is in az2. Then it can cause a volume node affinity error. How can we tackle this issue?

from mongodb-kubernetes-operator.

kube-scheduler accounts for the fact that the volume is in a specific az and will schedule the pod in the correct az

from mongodb-kubernetes-operator.

If a pod is rescheduled, deleted and recreated, or an instance where the pod was running is terminated then a pod reuses an existing EBS volume there is still a chance that the pod will be scheduled in an AZ where the EBS volume doesn’t exist.

I'm getting volume node affinity error in above scenario. Kube-schedule won't be able to schedule the pod in the correct az where the volume exist.

from mongodb-kubernetes-operator.

This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.

from mongodb-kubernetes-operator.

This issue was closed because it became stale and did not receive further updates. If the issue is still affecting you, please re-open it, or file a fresh Issue with updated information.

from mongodb-kubernetes-operator.