SMCP status changes to PausingUpdate after applying nodeSelector and podAntiAffinity

Solution In Progress - Updated -

Issue

  • ServiceMesh misbehaves after applying nodeSelector and podAntiAffinity the SMCP goes from STATUS ComponentsReady to PausingUpdate.

Environment

  • Red Hat OpenShift Container Platform
    • 4.x
  • Red Hat OpenShift Service Mesh
    • 2.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