Closed jtorrex closed 1 month ago
This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.
This issue was closed because it became stale and did not receive further updates. If the issue is still affecting you, please re-open it, or file a fresh Issue with updated information.
What did you do to encounter the bug? Steps to reproduce the behavior:
What did you expect?
I expected that the annotation (volumeName) defined in the MongoDB statefulSet.spec will be populated to the newly created PersistentVolumeClaims.
What happened instead?
The PersistentVolumeClaim creates a new volume and isn't binded to the volumeName defined in the manifest.
Operator Information
Kubernetes Cluster Information
Additional context The idea was to mount a pre-existing PersistentVolume that I had, so following the official Kubernetes documentation, it can be bound to a PVC defining their name in the Spec section: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#binding