`allowedSourceRanges` should support ipv6

[viceice]

Please, answer some short questions which should help us to understand your problem / question better?

• Which image of the operator are you using? ghcr.io/zalando/postgres-operator:v1.13.0
• Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal K8s
• Are you running Postgres Operator in production? yes
• Type of issue? feature request

I've a cluster which supports dualstack networking and i like to allow ipv6 access to my postgresql clusters.

To get this working i need to set ipv6 ranges to allowedSourceRanges to the postgresql crd.

it should also be possible to set the ipFamilyPolicy and ipFamilies fields on the service opbjects.

Workaround: Create my own service

Error:

postgresql/db/pgc1 dry-run failed (Invalid): postgresql.acid.zalan.do "pgc1" is invalid: [spec.allowedSourceRanges[1]: Invalid value: "fd01::/48": spec.allowedSourceRanges[1] in body should match '^(\d|[1-9]\d|1\d\d|2[0-4]\d|25[0-5]).(\d|[1-9]\d|1\d\d|2[0-4]\d|25[0-5]).(\d|[1-9]\d|1\d\d|2[0-4]\d|25[0-5]).(\d|[1-9]\d|1\d\d|2[0-4]\d|25[0-5])/(\d|[1-2]\d|3[0-2])
\(']

[FxKu]

I welcome a PR that updates the pattern for allowedSourceRanges field to allow all the stuff you've mentioned @viceice :smiley:

[ManjunathCV91]

Any plans to include this feature ? I also want to install PostgreSQL in dual stack openshift cluster.

if any other workaround please suggest.

[AlyHKafoury]

@FxKu I would love to work on this, is that ok ?

[amk9978]

Any updates on this? @AlyHKafoury @FxKu

[AlyHKafoury]

I am interested to work on this, but got no answer if it is ok to start working on it

[viceice]

I don't have time to work on this