VolumeAttributeClass not properly handled by the operator #1818
Description
We are evaluating the use of VolumeAttributeClass to dynamically adjust EBS volume parameters for performance testing across multiple configurations, in order to identify the setup that best fits our requirements.
From this issue and from my own testing, it seems that volumeAttributesClassName is correctly applied when declared in volumeClaimTemplates.
However, I’ve noticed the following behavior when working with existing clusters:
- If I add volumeAttributesClassName where it was not previously defined, the operator does not apply it.
- If I update the value of volumeAttributesClassName, the change is not propagated.
In both cases, I need to manually patch the PVC from the command line to have the changes in place, coherently with the helm chart definition.
Apparently is an operator issue, can you please address it?
I think it's worth stressing that also the desired behavior when adding volumeAttributesClassName to a pre-existing PVC would be to avoid volume re-creation.
Thank you!