Pod placement not equally done across multiple zones

Solution Verified - Updated -


  • In some cases, pods gets scheduled in the same zone even if two identical zones with identical pods are available. We are using custom labels and have adjusted scheduler.json to implement anti-affinity based on these labels. The scheduler.json was extended with the following entry to achieve service-anti-affinity.
            "argument": {
                "serviceAntiAffinity": {
                    "label": [ "datacenter" ]
            "name": "Datacenter",
            "weight": 10


  • Red Hat OpenShift Container Platform 3.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content