Kevin Taylor

Shouldn't it be the same consistent endpoint as the ui ``` http://10.6.141.180:4400/v1/scheduler/jobs ```

Perhaps --http_address = 0.0.0.0 could be the factor - you might also wish to try localhost:4400 first and see whether the port is actual available for listening.

When I perform the same approach here, I get a different version. As far as I can recall we are using v3.0 of chronos, which gives this ``` HTTP/1.1 200...

@brancz Was there any update on this? - we get spammed a lot on our alerts with this false detail

Hi. Thanks for this answer but... We are using the helm chart which has this baked in: https://github.com/coreos/prometheus-operator/blob/master/helm/exporter-kubernetes/templates/kubernetes.rules.yaml How do we influence that? And if I do want to programmatically...

@gianrubio Do you have any helm updates to fix this?

@brancz Is this project still active? We don't seem to get any responses

I think also that this PR may be related to this issue: prometheus-operator/prometheus-operator#2058

@pingles I am not sure if this is related or not but I am having difficulties getting the assume-role-arn to work ``` {"level":"error","msg":"error requesting credentials: AccessDenied: User: arn:aws:sts::034324643013:assumed-role/us-west-2-md-Controller/i-084d38eaacc983616 is not...

@pingles Thanks, will do