Helm deploy failed to pass in custom configuration

[zzhao2010]

Helm deploy failed to pass in custom configuration

[yorugac]

Hi @zzhao2010,

prometheus:
  enabled: true
  prometheusSpec:
   ...

Which chart is configured with these values? k6-operator's chart cannot be configured in this way. This looks like an issue with your setup rather than with k6-operator.

Given the error, one thing that is worth checking is the URL for Prometheus:

        value: "http://prometheus-kube-prometheus-prometheus:9090/api/v1/write"

This assumes that Prometheus is in default namespace: context timeout suggests that k6 runners cannot reach it with this URL - it may be incorrect or incomplete. I'd double-check that part. But overall, it seems like an issue with setup rather than a bug here.

[zzhao2010]

@yorugac
Turned out the issue was with the url. Because the prometheus pod and k6 pod are hosted on different namespace, the endpoint needs to include the namespace like http://prometheus-kube-prometheus-prometheus..svc.cluster.local:9090/api/v1/write..

Another question regarding the prometheus.enabled value in the doc in k6-operator chart, what does it do? The description didn't explain it clear. Does it have to be enabled for metrics reporting to Prometheus correctly?

[yorugac]

prometheus.enabled is for creating ServiceMonitor: that option is meant for users of Prometheus Operator.

Glad you resolved it. I'm closing this issue as it is not a bug of k6-operator. As future reference, it is recommended to raise inquiries regarding k6-operator in community forum.