PMM-14364 Fix Patroni's pg_hba subnets #658
Merged
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.
This pull request updates the PostgreSQL host-based authentication (pg_hba) configuration for Patroni to better support common private network ranges used in Kubernetes environments. The main change is a shift from hardcoded network ranges to a more flexible and comprehensive configuration that covers major cloud providers and on-prem setups.
Patroni configuration updates:
In
charts/pmm-ha/values.yaml, thepg_hbaentries underpatroni.dynamicConfiguration.postgresqlhave been updated to allow connections from RFC1918 private networks (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) for bothgfuserandpmmuser, improving compatibility with AWS, GCP, Azure, Docker, minikube, and on-prem environments.In
charts/pmm-ha/charts/pg-db/values.yaml, the previous hardcodedpg_hbaentries for specific subnets have been replaced with an empty list, delegating the configuration to the parent chart and preventing conflicting or redundant settings.