Repository navigation
Conversation
cardoe
force-pushed
the
neutron-mariadb-connection-snippet
branch
3 times, most recently
from
October 22, 2026 20:07
a8e00e4 to
21cec82
Compare
cardoe
marked this pull request as ready for review
October 22, 2026 20:07
Have the neutron chart declare the Database, User, Grant and Connection resources and project the operator-written neutron-db-conn secret into every workload that talks to the database, instead of generating a [database] connection from the NEUTRON_DB_PASSWORD Helm value. The password is read from the existing neutron-db-password secret (mariadb_db.password_secret.create: false) and the resources attach to the MariaDB named mariadb (mariadb_ref) while clients keep connecting through the mariadb-primary service. This needs a neutron chart carrying the mariadb_db.password_secret and mariadb_db.mariadb_ref values; the chart pin must be bumped before this syncs. components/neutron/neutron-mariadb-db.yaml is no longer needed and NEUTRON_DB_PASSWORD is dropped from openstack-secrets.tpl.yaml.
cardoe
force-pushed
the
neutron-mariadb-connection-snippet
branch
from
October 22, 2026 20:17
21cec82 to
651bb8e
Compare
Convert placement the same way as neutron: the chart declares the Database, User, Grant and Connection resources and the operator-written placement-db-conn secret is projected into the db-sync job and the API instead of generating a [database] connection from PLACEMENT_DB_PASSWORD. Bump the placement chart to 2026.2.3, which carries the mariadb_db values. components/placement/placement-mariadb-db.yaml is removed and PLACEMENT_DB_PASSWORD is dropped from openstack-secrets.tpl.yaml. The kustomization is left with an empty resources list because the Argo application always adds components/placement/ as a source.
Convert glance the same way as neutron and placement: the chart declares the Database, User, Grant and Connection resources and the operator-written glance-db-conn secret is projected into the API, the db-sync job and the metadefs-load job (which runs glance-manage against the database) instead of generating a [database] connection from GLANCE_DB_PASSWORD. Bump the glance chart to 2026.2.3, which carries the mariadb_db values. components/glance/glance-mariadb-db.yaml is removed and GLANCE_DB_PASSWORD is dropped from openstack-secrets.tpl.yaml.
Convert keystone the same way as neutron, placement and glance: the chart declares the Database, User, Grant and Connection resources and the operator-written keystone-db-conn secret is projected into the API, the db-sync job and the credential-rotate cronjob (credential_migrate touches the database) instead of generating a [database] connection from KEYSTONE_DB_PASSWORD. Bump the keystone chart to 2026.2.3, which carries the mariadb_db values. components/keystone/keystone-mariadb-db.yaml is removed and KEYSTONE_DB_PASSWORD is dropped from openstack-secrets.tpl.yaml.
cardoe
changed the title
cardoe
changed the title
haseebsyed12
approved these changes
Oct 22, 2026
Contributor
Author
|
Wait to merge this. Might try to fix up the operator to make the upgrade instructions easier. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Have the MariaDB operator render the database connection for neutron,
placement, glance and keystone, instead of generating a
[database] connectionfrom each service's<SERVICE>_DB_PASSWORDHelm value.Each chart declares the Database, User, Grant and Connection resources, and the
operator-written
<service>-db-connsecret is projected into every workloadthat talks to the database. The password is still read from the existing
<service>-db-passwordsecret.Chart pins are bumped to 2026.2.x releases carrying the
mariadb_dbvalues,components/<service>/<service>-mariadb-db.yamlis removed and<SERVICE>_DB_PASSWORDis dropped fromopenstack-secrets.tpl.yaml.One commit per service. Cinder is not included: its
cinder-binconfigmapoverride has drifted from upstream and needs its own review.
Deploy repos need the
<service>-db-passwordsecrets to exist before thissyncs; see the changelog fragment for the Grant cleanup steps.