Is it mandatory for pyrra and prometheus to have same mount point?

[mehtameet9]

we already have a prometheus running in our production system which has a volume mount for path /etc/config which was installed without prometheus operator
we are in process of adding pyrra to our tech stack but facing few challenges related to the same can someone explain how the reconcilation works and how pyrra will generate rules that will be consumed by our exisiting prometheus
REF: https://github.com/pyrra-dev/pyrra/tree/main?tab=readme-ov-file#running-inside-a-kubernetes-cluster

[mehtameet9]

also i tried running pyrra in kubernetes mode by following https://github.com/pyrra-dev/pyrra/tree/main?tab=readme-ov-file#running-inside-a-kubernetes-cluster

but for my use case i need to run it in the configmap mode by enabling --config-map-mode=true, which i did but im seeing pyrra still tries to generate a PrometheusRule CRD instead of generating the config maps

2024-08-19T15:17:44Z ERROR Reconciler error {"controller": "servicelevelobjective", "controllerGroup": "pyrra.dev", "controllerKind": "ServiceLevelObjective", "ServiceLevelObjective": {"name":"prometheus-query-errors","namespace":"terraform"}, "namespace": "terraform", "name": "prometheus-query-errors", "reconcileID": "ee871f15-a0a0-4c9f-9946-e38968592980", "error": "failed to get prometheus rule: failed to get API group resources: unable to retrieve the complete list of server APIs: monitoring.coreos.com/v1: the server could not find the requested resource"}

any help would be really appreciated, thanks

i can similar issues being reported
#1244