Skip to content
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

Disable cluster relationship from the main side. #2075

Closed
russjones opened this issue Jul 13, 2018 · 2 comments
Closed

Disable cluster relationship from the main side. #2075

russjones opened this issue Jul 13, 2018 · 2 comments
Assignees

Comments

@russjones
Copy link
Contributor

russjones commented Jul 13, 2018

For these examples I'll assume that we the following trusted cluster relationship: main.example.com<-remote.example.com.

Remove Trusted Cluster relationship from both sides

Once established, to fully remove a trust relationship between two clusters, do the following:

  1. Remove the relationship from the remote side: tctl rm tc/main.example.com.
  2. Remove the relationship from the main side: tctl rm rc/remote.example.com.

Remove Trusted Cluster relationship from the main side

  1. Remove the relationship from the main side: tctl rm rc/remote.example.com.

Note: The remote.example.com cluster will continue to try and ping the main cluster, but will not be able to connect. To re-establish the trusted cluster relationship, the trusted cluster has to be create again from the remote side.

Remote Trusted Cluster relationship from the remote side

  1. Remove the relationship from the remote side: tctl rm tc/main.example.com.
@okanturksever
Copy link

okanturksever commented Oct 24, 2018

Hi @kontsevoy,
I'am also trying to disable trusted clusters completely, I think there is something missing in your fix. Could you check it? You added like;

execute on "main":
$ tctl rm tc/east
execute on "east":
$ tctl rm tc/main

I think it should be like;
execute on "main":
$ tctl rm rc/east
execute on "east":
$ tctl rm tc/main

@russjones , I applied it like that, but in "main" cluster, I get this warning in proxy log.
WARN cluster "east" is not found web/apiserver.go:1877
I checked that the clusters are seperated (tsh clusters). But "main" proxy is still tring to reach "east".

@okanturksever
Copy link

update:
@russjones please ignore that, I forgot to refresh my browser :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants