When using database secrets or connection details managed by the
mariadb-operator for example, the automatic injection of the
database.connection into the service .conf file is detrimental. This
allows users to disable that magic by explicitly setting the connection
to the value of 'null' and leaving the replacement behavior in place for
other cases. The existing charts used 'null' in some cases but its a
cleaner case to handle 'null' for this so switch them to defaulting to
the empty string.
Add values_overrides/<chart>/mariadb-operator.yaml for all 26
charts showing how to opt out of chart-managed database connection
strings when using mariadb-operator. Each override sets the
relevant connection key(s) to null and disables the db-init,
and db secret manifests that are no longer needed when the
operator manages the database lifecycle.
To opt out of chart-managed connection strings (e.g. when using
mariadb-operator to supply them via a mounted configuration snippet),
set the relevant key to null in a values override:
conf:
keystone:
database:
connection: null # mariadb-operator provides [database]
Other keys in the database section (max_retries, etc.) are
unaffected and continue to be rendered normally.
Assisted-by: Claude Sonnet 4.6 <claude-sonnet-4-6@anthropic.com>
Change-Id: I7385dfb67f3d8899a8c3d1479b06f2ae21bc5791
Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
ae0f184773