Conversation
|
Full scan comparison results are too large to post as a comment. Link to full results artifact: Results quay.io/prometheuscommunity/postgres-exporter
|
1 participant
{{ message }}
Closed
Contributor
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.
Description
The pgbouncer image provided by RapidFort is not configured to work with the upstream chart. This PR adds a test that proves pgbouncer does not deploy correctly, then it sets the correct environment variables and security context for pgbouncer to operate.
The
enableConnectPoolervar is also added to simplify deploying PGBouncer.To reproduce the error and run the test:
spec.enableConnectionPoolerto true inpostgres-minimal.yamluds run -f tasks/test.yaml configure-pgbouncerRelated Issue
Relates to
https://github.com/defenseunicorns/mission-success/issues/586
Type of change
Checklist before merging