Grafana MultiNamespace Support - DataStorage: VolumeName is not working as expected / ServiceAccount

[Maximilian-Pfau-P]

Use-Case: We need multiple Grafana Instances within the same namespace and don't want to use an additional external database. The Operator has hard-coded values for service, route etc. but those values can luckily be changed in the operator configuration. Unfortunately for setting the name of the PVC we are running into an error.

Describe the bug
We set the volumeName under dataStorage:

OperatorConfig:
dataStorage:
accessModes:
- ReadWriteMany
class: sc-name
size: 100Mi
volumeName: pvc-name

Error-Message: "Object <>/grafana-pvc is already owned by another Grafana controller cluster"

Since there isn't much documentation regarding this topic I'm just gussing that this parameter is only for specifing the underlying PV and the name of the pvc can't be changed?

As far as I understand the same problem exists for the ServiceAccount, we only can deactivate the management of the serviceaccount and create it manually. I would also prefer a managed solution here.

Would it be possible to implement those paramaters?

Version
grafana-operator.v4.9.0

Additional Comments
volumeName is not referenced in following doc
https://github.com/grafana-operator/grafana-operator/blob/master/documentation/deploy_grafana.md

But is included in the CRD:
https://github.com/grafana-operator/grafana-operator/blob/master/documentation/api.md

[NissesSenap]

This seems to be a duplicate of #174, this will be supported I think your use case will be solved in version 5 of the operator.
We hope to release an RC of v5 sometime this or next week, and if this still don't solve your issue please open a new one.