Versions (relevant - OpenSearch/Dashboard/Server OS/Browser):
Opensearch 2.19.0
Describe the issue :
The precreated PV for mounting files across nodes, when configured as part of opensearch-cluster.yaml file under additional volumes does not work. opensearch-operator throws error during installing the cluster.
Configuration :
spec:
general:
additionalVolumes:
- name: my-fileshare-pvc
persistentVolumeClaim:
claimName: my-fileshare-pvc
path: /usr/share/opensearch/custom
Relevant Logs or Screenshots :
pablo
April 24, 2025, 1:28pm
2
Where did you find this configuration? According to the documentation the only supported objects are ConfigMaps, Secrets, emptyDir, projected volumes and CSI volumes.
@pablo , Got it, just trying to understand if this will not be supported at all by operator or is part of any future scope to support additional PV. Because without operator, normal helm deployments does support additional pv mount. Also, even eck operator supports additional PV mount for elastic when looking from a parity perspective.
Thanks!
pablo
April 25, 2025, 2:51pm
4
@Nagpraveen Are you referring to OpenSearch helm charts? If so, could you point out where they are supported? I’m only aware of the persistence for the node data.
seLinux:
rule: RunAsAny
supplementalGroups:
rule: RunAsAny
volumes:
- secret
- configMap
- persistentVolumeClaim
- emptyDir
persistence:
enabled: true
# Set to false to disable the `fsgroup-volume` initContainer that will update permissions on the persistent disk.
enableInitChown: true
# override image, which is busybox by default
# image: busybox
# override image tag, which is latest by default
# imageTag:
labels:
# Add default labels for the volumeClaimTemplate of the StatefulSet
enabled: false
@pablo : Greetings!!
Yes, indeed the common pv is supported under extraVolumes under opensearch helm deployment.
Node’s individual persistence also is anyways supported.
Below is the working config for additional pv using helm deployment
extraVolumes:
- name: fileshare-pv
persistentVolumeClaim:
claimName: fileshare-pvc
extraVolumeMounts:
- name: fileshare-pv
mountPath: /usr/share/opensearch/config/custom
pablo
April 29, 2025, 4:38pm
6
@Nagpraveen Thanks for sharing, I missed that part.
Regarding the lack of support for PVC in additionalVolumes, I suggest opening a Feature Request in the Operator’s GitHub .
If you do so, please share the link to the GitHub feature request here.
1 Like
@pablo : Thank you for the review and suggestion.
I have opened up a feature request as advised:
opened 06:31PM - 29 Apr 25 UTC
enhancement
untriaged
### Is your feature request related to a problem?
Currently, when opensearch hel… m charts are used for deploying an opensearch cluster, the common persistence volume (PV) is supported well under extra volume and extra volume mounts as shown below:
`extraVolumes:
- name: fileshare-pv
persistentVolumeClaim:
claimName: fileshare-pvc
extraVolumeMounts:
- name: fileshare-pv
mountPath: /usr/share/opensearch/config/custom`
However, when trying create the opensearch cluster via **opensearch operator**, the above extra volumes does not work. As per the doc, only ConfigMaps, Secrets, emptyDir, projected volumes and CSI volumes are supported, which makes it hard in certain. use-cases to integrate the persistent volume using above methods.
### What solution would you like?
From compatibility view point, the extravolume must also be supported by the operator so that the pv can be mounted across the desired nodes seamlessly.
### What alternatives have you considered?
a) config map supports till 1 mb
b) csi via gcp fuse makes use of gcs bucket, which requires additional principal roles for service accounts.
### Do you have any additional context?
The ECK operator also supports the common pv mount from a parity view point.
Thanks!
1 Like