This article will provide answers to some frequently asked questions on HCP Vault upgrade process.
Will there be any downtime or service interruptions?
The upgrade process for HCP Vault follows the recommended upgrade process for Vault and is managed entirely by the platform. In the linked guide it is mentioned:
"Please note that Vault does not support true zero-downtime upgrades, but with proper upgrade procedure the downtime should be very short (a few hundred milliseconds to a second depending on how the speed of access to the storage backend)."
In most cases, there is no client impact if clients are configured to retry requests.
What is the schedule for HCP Vault updates?
For production clusters, we currently provide users the option of a US and EU/UK maintenance window. The default window will be automatically assigned to occur at the same time as the Vault cluster region. In the future, we plan to support user-initiated major upgrades and 2 major versions (the current and one prior). Minor upgrades will be maintained within each major release family such that the most recent stable version will be deployed.
Can I opt out of automatic updates for HCP Vault?
It is not possible to opt out of automatic major version updates for Development or Starter tier. However, major version upgrade settings (automatic, scheduled, manual) are available on either the Standard or Plus tier. Please review the documentation for more information.
Does HCP Vault allow static versions of HCP Vault to be installed?
We currently do not support static versions for HCP Vault.
Please see our documentation for more information on HCP Vault upgrades
For additional questions or support, please open a Support ticket.