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

vault + consul cross DC setup #93

Open
Niranjankolli opened this issue Feb 9, 2020 · 1 comment
Open

vault + consul cross DC setup #93

Niranjankolli opened this issue Feb 9, 2020 · 1 comment

Comments

@Niranjankolli
Copy link

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. ?

@catsby
Copy link
Member

catsby commented Feb 11, 2020

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.

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

No branches or pull requests

2 participants