Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup monitoring/prometheus-operator-kube-proxy metrics #1636

Closed
vijay-veeranki opened this issue Feb 7, 2020 · 1 comment
Closed

Setup monitoring/prometheus-operator-kube-proxy metrics #1636

vijay-veeranki opened this issue Feb 7, 2020 · 1 comment
Assignees

Comments

@vijay-veeranki
Copy link
Contributor

vijay-veeranki commented Feb 7, 2020

With the promethus-operator upgrade to 8.7.0, we now have a option to get option to scrape kube-proxy. But as it is available in kube-system, we are not able to get the metrics and getting the below error

https://prometheus.cloud-platform.service.justice.gov.uk/targets#job-monitoring%2fprometheus-operator-kube-proxy%2f0

Investigate options to get it working.

helm/charts#16476
kubernetes/kops#6472 (comment)

From the values file.

## Component scraping kube proxy
##
kubeProxy:
  enabled: true

  ## If your kube proxy is not deployed as a pod, specify IPs it can be found on
  ##
  endpoints: []
  # - 10.141.4.22
  # - 10.141.4.23
  # - 10.141.4.24

  service:
    port: 10249
    targetPort: 10249
    # selector:
    #   k8s-app: kube-proxy

  serviceMonitor:
    ## Scrape interval. If not set, the Prometheus default scrape interval is used.
    ##
    interval: ""
@AntonyBishop
Copy link
Contributor

Related to #1850

@jasonBirchall jasonBirchall self-assigned this May 26, 2020
jasonBirchall added a commit to ministryofjustice/cloud-platform-infrastructure that referenced this issue Jun 8, 2020
This allows Prometheus to scrape the kubeProxy endpoint as outlined in ministryofjustice/cloud-platform#1636
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants