rebase #8
Merged
rebase #8
Conversation
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
These structured fields are easier and safer to use than raw HBA records. The validation rules of Kubernetes 1.29 (Beta in 1.25) allow for this kind of structure. Co-authored-by: TJ Moore <[email protected]> Issue: PGO-2263
The differences between "password," "md5," and "scram-sha-256" are not interesting to Postgres novices. This allows one to say "password" in the API and have secure authentication using usernames and passwords. The PGO default "password_encryption" has always been "scram-sha-256". Issue: PGO-2263
Add pgadmin/gunicorn log rotation configuration This PR continues the project of adding log retention configuration for users who have turned on the OTEL logging feature gate. This PR also makes some changes to our pgAdmin configuration. * Parse log retention in spec to use in pgadmin and gunicorn configuration * Restart gunicorn if logging changes to create new logger. (This is due to gunicorn behavior.) * Change the way we add a /tmp dir to pgAdmin to add to all containers. * Have the collector container create the receiver dir it needs. * Change the way we add config: add it to the configmap rather than the pod. Issues: [PGO-2168]
Sets Patroni's 'standby_leader_label_value' setting to 'master' to make standby clusters compatible with Patroni v4. Issue: PGO-2293
PostgreSQL has stored passwords as SCRAM-SHA-256 since PostgreSQL 14. PGO has stored passwords as SCRAM-SHA-256 since PostgreSQL 10. The "spec.authentication.rules" and "spec.config.parameters" fields allow users to downgrade to MD5 when necessary. Issue: PGO-2290 See: https://www.postgresql.org/docs/current/auth-password.html
* regenerate verifier only when user updates pgBouncer Secret password * improve logic for calculating verifier * refactor to remove generatePassword func * added comment describing MD5/SCRAM requirements * added test for SCRAM verifier * refactored logic to clearly capture four possible events * refactored test * simplified logic * removed empty branch to pass linter * updated test to check for setting verifier only --------- Co-authored-by: Philip Hurst <[email protected]>
This adds some validation to the PGAdmin data volume spec. Tests show we can simplify these validation rules, which may help keep estimated validation costs low.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
No description provided.