1 個回答
- 最新
- 最多得票
- 最多評論
0
Use pod anti-affinity rules to spread pods across nodes. This prevents scheduling pods from the same application onto the same node. You can choose "preferredDuringSchedulingIgnoredDuringExecution" to make it a soft constraint. You can also set pod topology spread constraints to evenly distribute pods matching certain labels. This helps enforce distribution.
https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/ https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ https://www.youtube.com/watch?v=hv8lHqRZFJA&ab_channel=LukondeMwila
已回答 2 個月前
相關內容
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 個月前
- AWS 官方已更新 2 年前
Hi, I'm facing the same issue. Can you share us how you solved the problem?