zalando / zalando/postgres-operator
Expose services over NodePort
Open
Nobody has claimed this yet.
enhancement
help wanted
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
For migration purposes we must expose postgres outside of k8s cluster, our main exposure method is a NodePort.
It would be nice if cluster CRD will allow to alter service type to a NodePort and optionally specify a value for nodeport number
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
Start by locating the cluster CRD and the reconciliation path that creates the PostgreSQL Service. Trace how service type and an optional nodePort value are represented and validated. Done means the CRD can request NodePort exposure with an optional port and the resulting service reflects those settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100