You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on a vault multi DC setup with consul as backend storage.
3 nodes consul cluster in each DC with LAN clusters.
Using consul-replicate am replicating the data from source to destination.
Whenever I create the new secret engine, it is not getting replicated to secondary DC.
Once I restart vault in secondary DC am able to see the secret engine.
Keys/policies/users are getting replicated.
Hello - As mentioned in hashicorp/vault#674 and on the mailing list, while consul-replicate will certainly replicate the data this is not an officially supported way for multi-dc replication in Vault at this time, and no current plans to support it. Specifically from hashicorp/vault#674 :
This is definitely a "hope it works but it's definitely not officially supported" scenario
I recommend closing this issue, as it's not an issue with consul-replicate and not supported by Vault.
I am working on a vault multi DC setup with consul as backend storage.
3 nodes consul cluster in each DC with LAN clusters.
Using consul-replicate am replicating the data from source to destination.
Whenever I create the new secret engine, it is not getting replicated to secondary DC.
Once I restart vault in secondary DC am able to see the secret engine.
Keys/policies/users are getting replicated.
I followed hashicorp/vault#674.
Anyone achieved this setup. ?
The text was updated successfully, but these errors were encountered: