SMCP status changes to PausingUpdate after applying nodeSelector and podAntiAffinity
Issue
- ServiceMesh misbehaves after applying nodeSelector and podAntiAffinity the
SMCPgoes from STATUSComponentsReadytoPausingUpdate.
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.