Placement Rules' clusterSelector.matchExpression Not Resolving As Expected

Solution Verified - Updated -


When using PlacementRules on my ACM cluster and selecting clusters based on matchExpression key/value pairs my applications are placed on clusters that are incorrect.

For example given two clusters, one on Cloud=Amazon with Vendor=Openshift and another on Cloud=IBM with Vendor=Openshift, the following clusterSelector results in the application being placed on both clusters instead of just the Cloud=Amazon cluster.

    - key: vendor
      operator: In
      - OpenShift
    - key: Cloud
      operator: NotIn
      - IBM


  • Red Hat Advanced Cluster Management for Kubernetes

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