"Failed to create/update gateway mirror endpoints: resource name may not be empty" after upgrading to 2025.4.1

[devopsbarbarian]

In all my clusters, all service-mirrors running 2025.4.1 I get the message "Failed to create/update gateway mirror endpoints: resource name may not be empty" on RepairEndpoints. Generally multicluster seems to work, services are accessible. Any idea what resource name the error is about?

[alpeb]

I'm not aware of a particular issue causing that. Can you provide the debug-level logs and the manifest for the workload producing that error?

[devopsbarbarian]

alright, it seems it's been fixed after I switched to using controllers bundled with linkerd-multicluster chart. Previously I've been using my own chart with service-mirror deployments with success (since linkerd 2.14), however it seems that something's got changed recently

[alpeb]

Great, thanks for circling back. Indeed, the new way will avoid to keep track of any of those changes 👍