Add troubleshooting section to pod-to-pod-multicluster for required metadata in secret

[Majkel1999]

Adding Troubleshooting section to the pod-to-pod-multicluster task, as the required metadata for secrets in control plane namespace is not documented.

References:

• Document required metadata for cluster-credentials secret in linkerd namespace linkerd2#11542
• https://github.com/linkerd/linkerd2/blob/ce950d17c60eab8c7c2a3e67c130241f96056ac2/controller/api/destination/watcher/cluster_store.go#L63C1-L67

Signed-off-by: @Majkel1999 [email protected]

[alpeb]

The linkerd multicluster link command should be used to retrieve the Link resource and the other associated resources (including those Secrets) to have multicluster communication properly work. I understand it's not always possible to plug a call to this command in all deployment pipelines, but the manifests to use should still be sourced from this command which provides the ultimate source of truth. So I don't see why we need to single out specific metadata that is already provided, and that is required just like many other pieces of metadata in other linkerd resources.

[kflynn]

@Majkel1999, thanks for digging into this! I left some comments about how I think this could be improved. 🙂

[kflynn]

@Majkel1999, to @alpeb's point, I think it's very important to say here that these Secrets are meant to be managed by the linkerd multicluster link command. I'm OK with providing more details, but I feel that the real core thing we need to make sure people understand is that this error generally means that they haven't properly used linkerd multicluster link. 🙂

[kflynn]

"Linkerd" instead of "LinkerD". 🙂