feat(cluster): Support additional Pooler configuration fields #791
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.
Fixes #785
pooler.spec.pgbouncerTLS configuration fields.pooler.serviceTemplatefield to override the Service configuration for the pooler.Combining these options allows the chart to deploy a Pooler with a LoadBalancer service, using a TLS certificate that will be valid for clients connecting from outside of the kubernetes cluster.
Example:
The other client/service TLS/CA secret fields are added to the template for completeness.