From 058ddd5b9fb07bf83aed40912cc4926e83231e1a Mon Sep 17 00:00:00 2001 From: williamlardier Date: Fri, 3 Jan 2025 10:35:06 +0100 Subject: [PATCH] Switch to hard anti affinity preset for mongos This will help not having two mongos servers on the same node. Issue: ZENKO-4641 --- solution-base/mongodb/charts/mongodb-sharded/values.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solution-base/mongodb/charts/mongodb-sharded/values.yaml b/solution-base/mongodb/charts/mongodb-sharded/values.yaml index b55ebd4090..7e531b4744 100644 --- a/solution-base/mongodb/charts/mongodb-sharded/values.yaml +++ b/solution-base/mongodb/charts/mongodb-sharded/values.yaml @@ -680,7 +680,7 @@ mongos: ## @param mongos.podAntiAffinityPreset Mongos Pod anti-affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` ## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity ## - podAntiAffinityPreset: soft + podAntiAffinityPreset: hard ## Node affinity preset ## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity ##