Ensure all components have metadata.labels.name: declared

[cloudxabide]

Description

I am exploring Isovalent Cilium/Hubble and when I review the openebs namespace for network flows in the Hubble UI, there are a number of components that appear as "Unknown App" (using ports 9502/9503 and 9501). jiva-operator does display the app name in the Hubble UI.

Note: the the trailing "blank lines" are intentionally left in the output to show there is no name set

$  kubectl get pods -n openebs -o=jsonpath='{range .items[*]}{.metadata.labels.name}{"\n"}{end}'
openebs-jiva-csi-controller
openebs-jiva-csi-node
openebs-jiva-csi-node
openebs-jiva-csi-node
jiva-operator
openebs-localpv-provisioner
openebs-ndm
openebs-ndm
openebs-ndm
ndm-operator







$

Context

I am not (yet) certain about this, but I believe as more fine-grained access is applied to Cilium, the app-name will be relevant for controlling flows. From what I can deduce the pods "pvc-(uuid)-jiva-rep-{0-2}" and "pvc-(uuid)-jiva-ctrl-(uuid)" do not have a name label, and therefore show up as "Unknown App" in the Hubble UI

Possible Solution

I believe .metadata.labels.name needs to be declared for each pod managed by openEBS.

Screenshots