Releases: digitalis-io/vals-operator
v0.6.4
Upgrade `vals` backend
Templates support
Core libraries updates
What's Changed
- Fix Helm chart kubeVersion comparison error by @irasnyd in #34
- doc: Explain how to use literal values by @digiserg in #36
- feat: update backend vals to latest version by @digiserg in #37
- feat: update core libraries to latest versions by @digiserg in #38
New Contributors
Full Changelog: v0.6.0...v0.6.1
Bug fix to Vault Tokens
There is a conflict between vals
and the vals-operator
when setting up the VAULT_AUTH_METHOD
variable causing both vals-operator and vals to perform login every time the controller refreshes a secret. This release rewrites the HaschiCorp Vault code to avoid conflict.
What's Changed
- Correct chart version number by @digiserg in #29
- Bugfix: kubernetes login creates too many tokens by @digiserg in #32
Full Changelog: v0.5.0...v0.6.0
Adds support for ElasticSearch password rotation
Similar to the other databases, adding support for ElasticSearch
Password rotation for MySQL, Postgres and Cassandra
This release adds password rotation to MySQL, Postgres and Cassandra. Once the password has been synced from the Secrets Store, it can be configured to update the password for a selected username.
Adds support for HashiCorp login with Kubernetes
vals
does not yet support Kubernetes Authentication for Vault. We're adding this support to the controller. Also, it now checks whether the vault token is about to expire and renews it.
Helm chart fixes
Merge pull request #5 from digitalis-io/events-permissions Tidied up service account permissions, added permission to write events
Adds support to sync secrets between namespaces
This release adds a new reference syntax of ref+k8s://namespace/secret#key
which will allow you to grab a secret from a different namespace and keep it in sync as per defined TTL.