Ignoring resource labels during backup or restore

[bitfactory-henno-schooljan]

Background

I'm managing my Kubernetes resource deployments using Argo CD. This tool adds a specific label to all resources it manages, which is used to track which resources may be pruned during deployments. By default this label is app.kubernetes.io/instance, e.g. on a managed ConfigMap:

apiVersion: v1
data:
  foo: bar
kind: ConfigMap
metadata:
  name: config
  labels:
    app.kubernetes.io/instance: app

When backing up and restoring these resources using Velero, these labels naturally go into the backups as well.

The issue

This becomes a problem when restoring a copy of the application into another namespace using a namespace mapping. Because these labels get restored with the same values, Argo CD thinks these resources are part of the original application and, depending on the settings used, either reports them as pruneable (annoying) or deletes them again immediately (devastating).

Question

Is there a way to tell Velero to not back up or restore such a label, so GitOps tools like Argo CD do not assume ownership and leave them alone? I see options to exclude things at the namespace- and/or resource level, but not at the annotation/label level.