Releases: ricoberger/vault-secrets-operator
Releases · ricoberger/vault-secrets-operator
Version 1.17.0 / 2022-03-25
- Add option to create a NetworkPolicy via the Helm chart (#151) by @ScOut3R
- Add option to load
VAULT_ROLE_ID
andVAULT_SECRET_ID
from a volume (#148) by @swarren83
Version 1.16.5 / 2022-01-23
- Make aws region and vault header configurable (#145) by @yanyixing
- Add namespace to test-connection pod (#143) by @kirillmandrygin
Version 1.16.4 / 2021-12-19
Version 1.16.3 / 2021-12-17
Version 1.16.2 / 2021-12-07
Version 1.16.1 / 2021-11-28
- Add
args
value for Helm chart, to allow modifications of the arguments for the Vault Secrets Operator
Version 1.16.0 / 2021-11-16
- Add AWS and GCP auth methods by @karl0r (#132)
- Allow token renewal to be disabled by @jacobbraaten (#126)
- Enable annotations to be addedd to the service account by @jacobbraaten (#125)
Version 1.15.2 / 2021-10-25
Version 1.15.1 / 2021-09-01
- Ignore
null
values from Vault by @BeryJu - Update dependencies
Version 1.15.0 / 2021-06-27
Features
- Add Azure Auth Backend (#114) by @Pale-whale
Breaking Changes
- Set Vault address via environment variable (#113) by @jaredallard: It is now possible to set the Vault address via the
environmentVars
value in the Helm chart. The default value for thevault.address
is now a an empty string. - Fix CRD installation (#111) by @rxbn: The installation of the VaultSecret CRD now follows the Helm best practices. For that the CRD was moved to an
crds
folder and thecrd.create
value was removed.