zalando / zalando/postgres-operator
IPv6 Kubernetes cluster support?
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Please, answer some short questions which should help us to understand your problem / question better?
Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.8.2
postgres-operator 1.8.2
Where do you run it - cloud or metal? Kubernetes or OpenShift? [AWS K8s | GCP ... | Bare Metal K8s]
OCP 4.11
Are you running Postgres Operator in production? [yes | no]
Not yet, still in non-production, but going to be there
Type of issue? [Bug report, question, feature request, etc.]
question for any special security related configuration to support OCP platform
we had the postgres operator and DB cluster in IPv4 Kubernetes cluster successfully, but not sure whether IPv6 is supported or not by postgres operator, so want to check in advance.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. First determine whether postgres-operator 1.8.2 and its PostgreSQL clusters support IPv6 on OCP 4.11; done means documenting a supported configuration or identifying the required changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100