@howardjohn If the user does istioctl version --short=false or -o json I expect we want something like

sidecar version: version.BuildInfo{Version:"1.3.0", Pod: "productpage-1234-5678.default"}

We don't want to exec into each sidecar looking for UUIDs, or asking Kubernetes for image information do we?

@esnible definitely not exec into each proxy for performance reasons. I was thinking we could fetch it from pilot like istioctl proxy-status does. This may be a bit more complex than I originally thought, as we would need a new struct for sidecars since we don't know all the same information and need info like Pod.

I think we need some way to see this easily, but since we will have #17173 in 1.4 now I think this becomes lower priority. What do you think?

I have an implementation, not yet pushed because istio/pkg#72 must merge first. It does something reasonable when the output is --short=false, YAML, or JSON, and for the default it shows.

istioctl version
client version: 66676a6c52d4e00fdd24dfa35933fabc51965713-dirty
control plane version: 1.3.0
data plane version: 1.3.0: (9 proxies), 1.3.0-rc.2: (1 proxies)