Today, we do have some common situations concerning the meshes that we use to test istio and kiali

1) The version of Istio upstream installed on a cluster is different from istioctl which is installed on Jenkins slave which leads to a failure on the pipeline

2) Maistra doesn't provide an 'istioctl' and might be incompatible with upstream isctioctl command.

4) Maistra supported way to injection of the sidecar is the automatic injection and the present pipeline doesn't have this support

3) We are going to move to Central CI Jenkins on future so it might be complicated to configure the slaves specific.

Since the new way to deploy cloud native applications on Kubernetes is the operators (https://github.com/operator-framework/operator-sdk) which encapsulate everything on the operator container (including the ansible flavor), it will simplify the pipeline.