How can I use Velero for cluster migration while handling environment-specific references?

[mame-leadec]

Hello,

I want to use Velero to migrate workloads from a Production cluster to a Development cluster (or vice versa). Both clusters share the same architecture, with the Development cluster being scaled down in terms of storage, memory, and CPU.

For most resources, it’s perfectly fine to connect Velero to the S3 bucket of the Production cluster and restore them directly. However, some resources may still contain references to "prod", such as Secrets, ConfigMaps, IngressRoutes, and other environment-specific settings.

What’s the best way to handle these references during the migration to ensure that the workload in the Development cluster functions correctly after the restore?

[kaovilai]

see https://velero.io/docs/v1.15/restore-resource-modifiers/