-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add troubleshooting section to pod-to-pod-multicluster for required metadata in secret #1705
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Michał Kaleta <[email protected]>
Signed-off-by: Michał Kaleta <[email protected]>
The |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Majkel1999, thanks for digging into this! I left some comments about how I think this could be improved. 🙂
1. `cluster-credentials-<remote-cluster-name>` residing in `linkerd-multicluster` namespace (default, it may be different if you have changed it, during installation of `linkerd-multicluster` extension). | ||
2. `cluster-credentials-<remote-cluster-name>` residing in the LinkerD control-plane namespace -- usually `linkerd`. | ||
|
||
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: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@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
. 🙂
Multicluster setup requires 2 secrets on the `source` cluster to function correctly. | ||
|
||
1. `cluster-credentials-<remote-cluster-name>` residing in `linkerd-multicluster` namespace (default, it may be different if you have changed it, during installation of `linkerd-multicluster` extension). | ||
2. `cluster-credentials-<remote-cluster-name>` residing in the LinkerD control-plane namespace -- usually `linkerd`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Linkerd" instead of "LinkerD". 🙂
Adding
Troubleshooting
section to the pod-to-pod-multicluster task, as the required metadata for secrets in control plane namespace is not documented.References:
Signed-off-by: @Majkel1999 [email protected]