Operator fails "silently" to update Superset Cluster's resource

[Maleware]

Affected version

No response

Current and expected behavior

I could recreate the problem when changing the "data" storage size.Changing CPU or Memory resources seems to work (results in a Pod restart)

Possible solution

In order to capture this we either need webhooks or track the resources in the status of the custom resource and delete and recreate the statefulset (PVCs should be resized automatically?)

Additional context

No response

Environment

No response

Would you like to work on fixing this bug?

None