What did you do to encounter the bug?
Steps to reproduce the behavior:
- Create a MongoDB Community and override the volume claim template:

Apply the cluster.
What did you expect?
volume attribute class to propagate through the mongodb to the PVCs.
What happened instead?
PVCs has VolumeAttributeClass
Operator Information
- Operator Version 1.6.0
- MongoDB Image used 6.0.16
Kubernetes Cluster Information
- Distribution EKS
- Version 1.34
- Image Registry location (quay, or an internal registry)