Inspectors pod determination conflicts with common app.kubernetes.io/instance: {{ .Release.Name }} setting approach

[IngoHolder]

We have issues running MQ Container Inspector as the inspector is using label
app.kubernetes.io/instance to identify the MQ HA pods. However, it seems that it is using {{ .Release.Name }} for the instance label. Setting
app.kubernetes.io/instance: {{ .Release.Name }}
is a common approach and we have multiple other pods that have this label set. MQ inspector should use a combination of labels (e.g. /instance + /name) to identify the right QMgr pods or it needs to tolerate that a pod returned is not actually a queue manager pod. For us, the inspector terminates as it not only finds 3 HA Qmgr pods but actually 4 and the 1st one is not a QMgr pod.

[Andrew-Lees11]

Hello,
We are not able to use the app.kubernetes.io/name: ibm-mq because it is not a requirement that a customers deployment has set this label and requiring it would prevent the tool from being able to collect the must gather in those scenarios, however
the MQ container inspector tool already has a isQueueManagerPod which could be used in addition to the instance label for identifying queue manager pods.

[IngoHolder]

Please note that I tried both parameters: --qm-name and --pod-name. However, it seems that the tool is using app.kubernetes.io/instance with preference and that is not good as it does not allow to bypass any other pod that has the app.kubernetes.io/instance: {{ .Release.Name }} set. If I specify a --pod-name (better would be a --pod-name-prefix) then this should be used with prio.