Add docs to recreate peering token.

This commit is contained in:
Ashwin Venkatesh 2022-08-10 13:14:36 -04:00
parent ea2f5a4014
commit d42a042436
1 changed files with 10 additions and 0 deletions

View File

@ -237,3 +237,13 @@ To confirm that you deleted your peering connection, in `cluster-01`, query the
```shell-session
$ curl "localhost:8500/v1/health/connect/backend?peer=cluster-02"
```
## Recreate/Reset a peering connection
To recreate or reset the peering connection, a new peering token needs to be generated on the cluster where the `PeeringAcceptor` was created, which in this case is `cluster-01`.
This can be performed by creating/updating the annotation `consul.hashicorp.com/peering-version` on the `PeeringAcceptor`. If the annotation already exists, update its value to a version that is higher.
Once the above is done, repeat the steps in the peering process from saving your peering token so that you can export it to the other cluster. This will re-establish peering with the updated token.
-> **NOTE:** A new peering token is only generated upon manually setting and updating the value of the annotation `consul.hashicorp.com/peering-version`. Creating a new token will cause the previous token to expire.