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

Migration or adding ha_storage for existing vault instance #1619

Closed
rodosskiand opened this issue May 12, 2022 · 4 comments
Closed

Migration or adding ha_storage for existing vault instance #1619

rodosskiand opened this issue May 12, 2022 · 4 comments
Labels
lifecycle/stale Denotes an issue or PR that has become stale and will be auto-closed.

Comments

@rodosskiand
Copy link

Hi! I can't find info about the opportunity for switching to/adding ha_storage in the existing vault instance (managed by the operator).
I found a guide: https://learn.hashicorp.com/tutorials/vault/raft-ha-storage and this what I need: updating existing server. But I'm not sure how this can be done correctly via the operator.

In my case, I use s3 integrated storage and a single vault replica (size: 1). Can I just add ha_storage parameter (example raft):

  config:
    storage:
      s3:
        region: "us-east-1"
        bucket: "vault"
    ha_storage:
      raft:
        path: /vault/raft
    listener:

and change the size to 3 (for example)?

Or I should make any extra actions for adding ha_storage?

Thanks!

Copy link

Thank you for your contribution! This issue has been automatically marked as stale because it has no recent activity in the last 60 days. It will be closed in 20 days, if no further activity occurs. If this issue is still relevant, please leave a comment to let us know, and the stale label will be automatically removed.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR that has become stale and will be auto-closed. label Feb 25, 2024
@akijakya
Copy link
Contributor

Hi @rodosskiand, sorry for the late response! Did you manage to figure this out, if yes, could you share your findings? Thanks!

@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR that has become stale and will be auto-closed. label Mar 3, 2024
Copy link

github-actions bot commented May 5, 2024

Thank you for your contribution! This issue has been automatically marked as stale because it has no recent activity in the last 60 days. It will be closed in 20 days, if no further activity occurs. If this issue is still relevant, please leave a comment to let us know, and the stale label will be automatically removed.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR that has become stale and will be auto-closed. label May 5, 2024
Copy link

This issue has been marked stale for 20 days, and is now closed due to inactivity. If the issue is still relevant, please re-open this issue or file a new one. Thank you!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR that has become stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

2 participants