Feature Request: Support for extraPVCs #2126
Description
Proposal
We propose adding support for specifying extra PersistentVolumeClaims (extraPVCs) in the operator. This enhancement would allow users to define one or more additional volumes that can be mounted into the container at specified mount paths, independent of the main data volume managed by the operator.
The configuration could be modeled similarly to how other Kubernetes operators support sidecar or auxiliary volumes, using a new optional extraPVCs field, such as:
pxc:
extraPVCs:
- volumeClaimTemplates:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: shared
spec:
resources:
requests:
storage: 25Gi
storageClassName: local
volumeMode: Filesystem
accessModes:
- ReadWriteMany
mountPath: /mnt/app-data
readOnly: false
Use-Case
We have a scenario where our application stores certain domain-specific information into a shared volume that DB needs access to. This data is not part of the database itself, but is used in conjunction with queries and procedures. For example, it may contain reference files, large binary objects, or externally generated lookup tables.
Currently, the operator lacks support for attaching additional volumes beyond the main database storage.
Supporting extraPVCs would enable clean, declarative volume attachment while maintaining full compatibility with operator lifecycle management.
Is this a feature you are interested in implementing yourself?
Yes
Anything else?
No response