fix(e2e): make postgres fixture compatible with OpenShift#2002
Merged
Conversation
Signed-off-by: Seth Jennings <sjenning@redhat.com>
TaylorMutch
approved these changes
Jun 25, 2026
Collaborator
|
/ok to test 72ce6c2 |
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.
Summary
Make the e2e PostgreSQL deployment fixture compatible with OpenShift by addressing UID-based filesystem permission issues that occur when OpenShift assigns random UIDs to pods.
Changes
PGDATAenv var pointing to a subdirectory (/var/lib/postgresql/data/pgdata) so postgres creates and owns the directory it needs to chmod, bypassing the UID mismatchurifield to the postgres secret for connection string conveniencepostgres-dataandpostgres-runemptyDir volume mounts for proper filesystem isolationTesting
mise run pre-commitpasses (rust lint, format, license headers all green)Checklist