Is there an existing issue already for this feature request/idea?

• I have searched for an existing issue, and could not find anything. I believe this is a new feature request to be evaluated.

What problem is this feature going to solve? Why should it be added?

CloudNativePG currently provides automated support for a basic PodMonitor resource associated with a Cluster resource via the .spec.monitoring.enablePodMonitor option, as described in our "Monitoring with the Prometheus Operator" documentation.

Over time, we have received several requests to extend this feature by adding fields and capabilities from the upstream PodMonitor API for greater customisation.

However, this direction is at odds with our ongoing efforts to refactor and simplify the CloudNativePG codebase (see CNPG-I) and with our broader goal of providing clear guidance on integrating CloudNativePG with other CNCF projects now that we are part of the Sandbox.

Describe the solution you'd like

Begin deprecating the .spec.monitoring.enablePodMonitor field and improve the documentation referenced above. The cluster Helm chart could take responsibility for enhancing the integration between CNPG and Prometheus.

Describe alternatives you've considered

Add a PodMonitorTemplate feature; however, it requires maintaining a dependency on the interface, resulting in minimal overall benefit.

Additional context

N/A

Backport?

No

Are you willing to actively contribute to this feature?

Yes

Code of Conduct

• I agree to follow this project's Code of Conduct