Envoy Proxy Sidecar Injection Failures in Service Mesh environment

Issue

• The upstream version of Istio injects the sidecar by default if you have labeled the project. Red Hat OpenShift Service Mesh requires you to opt in to having the sidecar automatically injected to a deployment, so labelling the project is not required. This avoids injecting a sidecar if it is not wanted (for example, in build or deploy pods).

• The webhook created by Service Mesh checks the configuration of pods deploying into all projects to see if they are opting in to injection with the appropriate annotation.

• What checks can be performed if no sidecar is injected into an application managed by Service Mesh?