From bf208e0c8d7fc9279662e8cad887e50b5871eac7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Kaleta?= <45182543+Majkel1999@users.noreply.github.com> Date: Sun, 5 Nov 2023 21:59:19 +0100 Subject: [PATCH] Fix spelling mistakes MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Michał Kaleta --- linkerd.io/content/2.14/tasks/pod-to-pod-multicluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/linkerd.io/content/2.14/tasks/pod-to-pod-multicluster.md b/linkerd.io/content/2.14/tasks/pod-to-pod-multicluster.md index 8520838ffa..768bc2aec4 100644 --- a/linkerd.io/content/2.14/tasks/pod-to-pod-multicluster.md +++ b/linkerd.io/content/2.14/tasks/pod-to-pod-multicluster.md @@ -315,7 +315,7 @@ Multicluster setup requires 2 secrets on the `source` cluster to function correc 1. `cluster-credentials-` residing in `linkerd-multicluster` namespace (default, it may be different if you have changed it, during installation of `linkerd-multicluster` extension). 2. `cluster-credentials-` residing in the LinkerD control-plane namespace -- usually `linkerd`. -The second secret (in `linkerd` namespace) has a specific metadata requirements - `linkerd-destination` required the secret to contain following labels and annotations (assuming we are linking `east` cluster to `west` cluster): +The second secret (in `linkerd` namespace) has a specific metadata requirements. Labels and annotations shown below are neccessary for the control plane, to be able to retrieve the remote cluster credentials. Assuming we are linking `east` cluster to `west` cluster, the secret would have to contain below metadata: ``` metadata: