Upgrade strategies
Upgrade Vault
To upgrade the Vault, complete the following steps.
- Check the release notes of Vault for any special upgrade instructions. Usually there are no instructions, but it’s better to be safe than sorry.
- Adjust the spec.image field in the Vault custom resource. If you are using the Vault Helm chart, adjust the image.tag field in the values.yaml.
- The Vault Helm chart updates the StatefulSet. It does not take the HA leader into account in HA scenarios, but this has never caused any issues so far.
Upgrade Vault operator
v1.20.0 upgrade guide
The release of the Vault Operator v1.20.0 marks the beginning of a new chapter in the development of the Bank-Vaults ecosystem, as this is the first release across the project after it has been dissected and migrated from the original banzaicloud/bank-vaults
repository under its own bank-vaults
organization. We paid attention to not introduce breaking changes during the process, however, the following changes are now in effect:
- All Helm charts will now be distributed via OCI registry on GitHub.
- All releases will be tagged with
v
prefix, starting fromv1.20.0
.
Upgrade to the new Vault Operator by changing the helm repository to the new OCI registry, and specifying the new version numbers:
helm upgrade vault-operator oci://ghcr.io/bank-vaults/helm-charts/vault-operator \
--set image.tag=v1.20.0 \
--set bankVaults.image.tag=v1.20.0 \
--wait
Make sure to also change the bank-vaults
image in the Vault CR’s spec.bankVaultsImage
field to ghcr.io/bank-vaults/bank-vaults:1.20.x
.
Last modified October 27, 2024: chore(deps): Bump actions/setup-node from 4.0.4 to 4.1.0 (#245) (fee5168)