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.
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.