Appropriate method for identifying NSM version programmatically

[tangledbytes]

Overview

Service meshes like Istio, linkerd, NGINX service mesh etc. have their versions either in the docker images running within the pods or they place some sort of annotations on the resources to highlight the version of the component. But NSM places the "latest" tag in the image names and none of the annotations actually reveal version related information. This makes it difficult to identify the version of NSM resources running in the cluster by scanning it.

What could be the appropriate method for identifying NSM version?

References

https://github.com/layer5io/meshery/issues/1911

[stale[bot]]

This issue has been automatically marked as stale because it has not had activity in 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.