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
It would be useful for nomad to be able to fail over with no operator action to a secondary vault (or a list of vaults) if it has issues with the first one.
This would reduce the possibility of a vault issue taking down a nomad cluster.
Currently, the only way to have HA is to have a Vault DR standby, but that requires a manual promotion and an extra vault cluster to manage and run. And If not promoted in time, jobs would stop or not be able to restart.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
It would be useful for nomad to be able to fail over with no operator action to a secondary vault (or a list of vaults) if it has issues with the first one.
This would reduce the possibility of a vault issue taking down a nomad cluster.
Currently, the only way to have HA is to have a Vault DR standby, but that requires a manual promotion and an extra vault cluster to manage and run. And If not promoted in time, jobs would stop or not be able to restart.
The text was updated successfully, but these errors were encountered: