Repository navigation
chore(deploy): reseal dev database-connection secret after doadmin password rotation - #677
Merged
Merged
Conversation
dadiorchen
approved these changes
Oct 4, 2026
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
2 participants
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.
The dev Postgres password for user
doadminchanged . The dev SealedSecretdatabase-connectionstill holds the old password, so this service cannot connect to the database since then.This PR replaces
deployment/overlays/development/database-connection-sealed-secret.yamlwith the same connection string re-sealed with the current password. No other change. Prod and test are not touched.Impact (dev only): keycloak-treetracker-admin-api and treetracker-admin-api return 500 on every DB request (admin-client #1242, admin-api #676).
After merge: ArgoCD syncs the SealedSecret, then the pods must be restarted (delete pods) because the env var is read at start.
Verified: the new password was tested with psql against the dev DB.