We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
I've found issue with loadBalancerSourceRanges. Its absent in Helm chart for values.proxy.pgBouncer.expose section.
Due to CDR spec on https://github.com/percona/percona-postgresql-operator/blob/main/deploy/cr.yaml we can see that loadBalancerSourceRanges persist on line 72. However in Helm chart this parameter absent. You can see it in template file https://github.com/percona/percona-helm-charts/blob/main/charts/pg-db/templates/cluster.yaml (look at line 181 and below)
Please add this parameter in Helm chart.
Thank you.
The text was updated successfully, but these errors were encountered:
Hello @KosShutenko ,
the thing that Operator does not properly support it yet. It is fixed by #532 (or https://jira.percona.com/browse/K8SPG-389).
And will be propagated to helm chart after the release 2.3.0 this month.
Sorry, something went wrong.
This was fixed and now supported in the helm chart. https://github.com/percona/percona-helm-charts/blob/main/charts/pg-db/templates/cluster.yaml#L195
Please try it out.
spron-in
No branches or pull requests
Hello,
I've found issue with loadBalancerSourceRanges. Its absent in Helm chart for values.proxy.pgBouncer.expose section.
Due to CDR spec on https://github.com/percona/percona-postgresql-operator/blob/main/deploy/cr.yaml we can see that loadBalancerSourceRanges persist on line 72. However in Helm chart this parameter absent. You can see it in template file https://github.com/percona/percona-helm-charts/blob/main/charts/pg-db/templates/cluster.yaml (look at line 181 and below)
Please add this parameter in Helm chart.
Thank you.
The text was updated successfully, but these errors were encountered: