Bug Report

What is the issue?

In a CNI setup, init containers that try to make outbound connection will fail due to a timing issue between the CNI plugin modifying the pod iptables, and the proxy container coming up. The current workaround is to skip the outbound ports of the init containers. However, this only works if the skip port configuration is provided during the CNI installati

We'd like to make sure flagger is there if there's some contention. Also please add this to the loadtester chart

Description

Client Version: 0.4.3 	  GitSHA: 51fa5e6626f024aa3bd914efd0d0c34fa136021a
Server Version: v0.4.3 	  GitSHA: 51fa5e6```

Currently client version doesn't have 'v' as in server version.

Expected Behavior

➜  meshery git:(myMeshMap) mesheryctl version
Client Version: v0.4.3 	  GitSHA: 51fa5e6626f024aa3bd914efd0d0c3

Current Behavior
KubeCon EU talks are out. This talk needs to be added to the second section of this page - https://layer5.io/projects/service-mesh-performance.

It would be nice if this talk is embedded as a Youtube video on this page - https://github.com/layer5io/layer5/blob/master/collections/_project

What's in https://linkerd.io/2/reference/architecture/ does not reflect 2.3.