Releases: db-operator/db-operator
Releases · db-operator/db-operator
v2.6.1
v2.6.0
Version v2.6.0 is released
What's Changed
- Set db-operator version on database CR during full reconcile by @bobertrublik in #107
Full Changelog: v2.5.1...v2.6.0
v2.5.1
v2.5.0
v2.4.0
v2.3.0
Version v2.3.0 is released
What's Changed
- Replace phases in database status with events by @bobertrublik in #87
- just making the linter happy again by @allanger in #100
Full Changelog: v2.2.0...v2.3.0
v2.2.0
v2.1.1
v2.0.1
v2.1.0
Version v2.1.0 is released
What's Changed
Notes
Now it's possible to use templated credentials in DbUser
objects.
Example:
kind: DbUser
spec:
credentials:
templates:
- template: "{{ .Username }}"
name: USERNAME
secret: true
It works the same way as templated credentials for Databases
, but DbUsers
, since they down own ConfigMaps
, can't write to them. So it's required that templates[].secret
is set to true
.
Also, DbUsers
are now using same methods for managing k8s resources that Databases
use and it made it possible to implement cleanup
feature for users. Now, if spec.cleanup
is set to true
, the secret that is used by a DbUser
will get an owner reference.
Full Changelog: v2.0.0...v2.1.0