zalando / zalando/postgres-operator
Support Annotations on Volume in CRD
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
I would like to propose adding an additional field to the volume spec in the operator of annotations that behaves the same as any other annotation spec in Kubernetes. The reason I would like this feature is we use the aws-ebs-csi-driver, which supports tuning volume resources via annotation such as provisioned IOPS and throughput which is something we routinely need to do for our Postgres deployments.
-
Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.10.1
registry.opensource.zalan.do/acid/postgres-operator:v1.10.1 -
Where do you run it - cloud or metal? Kubernetes or OpenShift? [AWS K8s | GCP ... | Bare Metal K8s]
AWS EKS. -
Are you running Postgres Operator in production? [yes | no]
Yes -
Type of issue? [Bug report, question, feature request, etc.]
Feature request.
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 volume spec in the CRD and the operator code that handles volume configuration, then compare it with existing annotation fields. Run the relevant operator and CRD tests; done means a volume-level annotations field is accepted and behaves like other Kubernetes annotation specifications for the requested storage settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes, postgresql
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100