Skip to content

Releases: ricoberger/vault-secrets-operator

Version 1.17.0 / 2022-03-25

25 Mar 14:09
Compare
Choose a tag to compare
  • Add option to create a NetworkPolicy via the Helm chart (#151) by @ScOut3R
  • Add option to load VAULT_ROLE_ID and VAULT_SECRET_ID from a volume (#148) by @swarren83

Version 1.16.5 / 2022-01-23

23 Jan 21:41
Compare
Choose a tag to compare

Version 1.16.4 / 2021-12-19

19 Dec 15:27
Compare
Choose a tag to compare

Version 1.16.3 / 2021-12-17

17 Dec 19:39
Compare
Choose a tag to compare
  • Fix Vault client initialization by adding renew token setting to each client by @Chumper (#140)
  • Add section about label propagation to readme by @Chumper (#139)

Version 1.16.2 / 2021-12-07

07 Dec 12:50
Compare
Choose a tag to compare
  • Split configmaps and leases in different entries in vault-secret-operator role by @ecojan (#137)

Version 1.16.1 / 2021-11-28

28 Nov 09:27
Compare
Choose a tag to compare
  • Add args value for Helm chart, to allow modifications of the arguments for the Vault Secrets Operator

Version 1.16.0 / 2021-11-16

16 Nov 20:47
Compare
Choose a tag to compare

Version 1.15.2 / 2021-10-25

25 Oct 15:52
Compare
Choose a tag to compare
  • Remove created-by label from the created Kubernetes secrets (#122)
  • Add Release.Namespace to all namespaced resources by @ecojan (#119)

Version 1.15.1 / 2021-09-01

01 Sep 17:05
Compare
Choose a tag to compare
  • Ignore null values from Vault by @BeryJu
  • Update dependencies

Version 1.15.0 / 2021-06-27

27 Jun 19:25
Compare
Choose a tag to compare

Features

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 the vault.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 the crd.create value was removed.