[Bug] Registry resource created by UI will have "matchOperator" portion (don't add any filter)

[williamshen9999]

UI Ext v0.6.0 + Backend v0.10.1

Steps (you can refer to the video below):

• Create a registry via UI (don't add any filter)
• For that created registry: Find UI will show "matchOperator" portion
• For that created registry: Find backend also has "matchOperator" portion (via kubectl as below)

Expected behavior:

As you can see, I don't add any filter when creating registry, so "matchOperator" should not be set in the registry source

filter-icon.mov

root@kw-sbom-ui-rke2-214-0316:~# k get registry quay-nvlab-alpine -o yaml
apiVersion: sbomscanner.kubewarden.io/v1alpha1
kind: Registry
metadata:
  creationTimestamp: "2026-03-16T08:49:55Z"
  generation: 1
  name: quay-nvlab-alpine
  namespace: default
  resourceVersion: "29342"
  uid: 9c830a30-32ce-44a4-b2a7-14a58a553b41
spec:
  authSecret: ""
  caBundle: ""
  catalogType: OCIDistribution
  insecure: false
  platforms: []
  repositories:
  - matchOperator: And
    name: nvlab/alpine
  uri: quay.io

[xingzhang-suse]

Hi @williamshen9999

It is not UI issue.Please file a github issue to backend team.
The UI does not submit any thing related to the matchOperator. It is generated from backend.