[dev-v2.9] rancher-monitoring: add ScrapeConfig CRD

[Carlotronics]

Problem

ScrapeConfig CRD is provided in prometheus charts but missing in rancher monitoring.

Solution

Add ScrapeConfig CRD

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:-
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.

[joshmeranda]

@Carlotronics can you give us some more context? Is this causing issues on your system, point us to the ScrapeConfig definition in kube-prometheus-stack-45.31.1, etc?

[alexandreLamarre]

From the docs

ScrapeConfig CRD :

Starting with prometheus-operator v0.65.x, one can use the ScrapeConfig CRD to > scrape targets external to the Kubernetes cluster or create scrape configurations that are not possible with the higher level ServiceMonitor/Probe/PodMonitor resources.

Which is supported, since we are using prometheus-operator:v0.65.1, but its absent from the upstream chart we use kube-prometheus-stack-45.31.1, taking a quick glance at the upstream chart commit history, these configs were added in around version 48.x which contains breaking changes to how the chart manages CRDs. So likely these will be supported during our next upgrade of the operator : rancher/rancher#44614