storage.sbomscanner.kubewarden.io.vulnerabilityreport cannot be seen in sbomscanner 0.7.0 from Rancher UI

[xingzhang-suse]

Hi @Fabrizio Sestito, May I ask a quick question?
I installed sbomscanner 0.7.0 and updated the UI code to reflect the backend project name change.
After triggering a scan through the UI, the status showed as Complete.
However, I don’t see the resource storage.sbomscanner.kubewarden.io.vulnerabilityreport in version 0.7.0.
The report can still be retrieved using the following command:

kubectl get vulnerabilityreport \
  --field-selector='imageMetadata.repository=kubewarden/sbomscanner/test-assets/golang,imageMetadata.platform=linux/amd64' \
  -n cattle-sbomscanner-system

Has storage.sbomscanner.kubewarden.io.vulnerabilityreport been deprecated in 0.7.0?
If not, I’ll continue investigating my environment and collect the relevant logs.
Thank you very much!

[xingzhang-suse]

I installed sbomscanner 0.7.0 and updated the UI code to reflect the backend project name change.
After triggering a scan through the UI, the status showed as Complete.
However, I don’t see the resource storage.sbomscanner.kubewarden.io.vulnerabilityreport in version 0.7.0.
The report can still be retrieved using the following command:

kubectl get vulnerabilityreport \
  --field-selector='imageMetadata.repository=kubewarden/sbomscanner/test-assets/golang,imageMetadata.platform=linux/amd64' \
  -n cattle-sbomscanner-system

The storage.sbomscanner.kubewarden.io.vulnerabilityreport has not been deprecated and it can still be accessed by kubectl.
However, in sbomscanner 0.7.0, I don’t see it under More resrouces menu in Rancher UI.

So after scanning, the image overview, detail page and CVE detail page cannot get the data by the current resource type.

According to Richard, this is probably something related to the change in group. but rancher (steve api) should pick anything like that up automatically

[xingzhang-suse]

The report resources appeared when I reloaded the page this morning.
It could be a environment performance issue. It caused the some timing issue when UI retrieves the resource through Rancher UI / Steve API.
Today, I tested it in another environment which is faster than that one. After scan finished, image data and vulnerability report can be seen in the page.