Scrapeconfig proxyUrl validator does not allow socks5 #7458
Description
Is there an existing issue for this?
- I have searched the existing issues
What happened?
Description
We are using a socks5 proxy in v1/Prometheus objects, using .spec.additionalScrapeConfigs.proxy_url (url socks5://bla), and would like to convert the additional scrape config to v1alpha1/ScrapeConfig. The CRD for these, however, validate proxyUrl using pattern ^http(s)?://.+, which don't allow socks5:// URLs.
Steps to Reproduce
apply this:
monitoring.coreos.com/v1alpha1
kind: ScrapeConfig
metadata:
name: crash
spec:
proxyUrl: socks5://127.0.0.1/
Expected Result
The resource to get applied
Actual Result
spec.proxyUrl in body should match '^http(s)?://.+$'
Prometheus Operator Version
0.77.1Kubernetes Version
1.32.3Kubernetes Cluster Type
Other (please comment)
How did you deploy Prometheus-Operator?
helm chart:prometheus-community/kube-prometheus-stack
Manifests
prometheus-operator log output
n/aAnything else?
We use FluxCD to provision these resources as part of a helm chart. It could be that it is either Helm or Flux doing this regex validation, but the origin of this regex pattern is the prometheus-operator CRDs.