The configuredMembers list in the SMMR resource gets cleared when the SMCP is being updated. This causes all member namespaces to appear to be removed from the mesh, which removes all their related services and pods from the service registry. This causes 503 errors across the mesh. Once the SMCP reconciliation completes, the member namespaces reappear in the configuredMembers list.

Steps to reproduce:

1. Create a mesh
2. Add a namespace to the mesh (e.g. bookinfo)
3. Deploy an application to the namespace (e.g. bookinfo)
4. Continuously route traffic through the mesh
5. Watch the status of the SMMR
6. Update SMCP

Notice that while the SMCP is being updated all requests destined for the namespace result in 503. Also notice that the status.configuredMembers list in the SMMR removes all members except the control plane namespace.