OLM - running in a restricted environment.

[rridtraining]

I'm trying to run OLM in a restricted kubernetes environment.
I was able to deploy OLM successfully, but when I try to subscribe to an operator, the manifest always takes a docker image like quay.io/image:tag instead of my-local-repository/image:tag.
I've seen that all manifests are in the /configs of the catalog docker image (quay.io/operatorhubio/catalog:latest), so I'm trying to rebuild the docker image but it doesn't take into account the changes I've applied.
Is there a configuration I can add to overwrite the docker repositories in the manifest in OLM catalog (quay.io/operatorhubio/catalog:latest)?

• To subscribe
  apiVersion: operators.coreos.com/v1alpha1
  kind: Subscription
  metadata:
  name: my-argocd-operator
  namespace: operators
  spec: channel: alpha
  name: argocd-operator
  source: operatorhubio-catalog
  sourceNamespace: olm

[github-actions]

Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.