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

prometheus returnd cannot validate certificate #1882

Closed
liyehaha opened this Issue Aug 10, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@liyehaha
Copy link

liyehaha commented Aug 10, 2016

Hi I had this problem when using prometheus in kubernetes.

The error log is:
ERRO[0000] Cannot initialize nodes collection: unable to list Kubernetes nodes: unable to query any API servers: Get https://172.60.0.1:443/api/v1/nodes: x509: cannot validate certificate for 172.60.0.1 because it doesn't contain any IP SANs source=node.go:124

The prometheus config file is:
`scrape_configs:

  • job_name: 'kubernetes-cluster'
    scheme: https
    tls_config:
    ca_file: /var/run/kubernetes/cert/ca.crt
    key_file: /var/run/kubernetes/cert/kubelet.key
    cert_file: /var/run/kubernetes/cert/kubelet.crt
    insecure_skip_verify: true

    kubernetes_sd_configs:

  • job_name: 'kubernetes-node'
    scheme: https
    tls_config:
    insecure_skip_verify: true
    ca_file: /var/run/kubernetes/cert/ca.crt
    key_file: /var/run/kubernetes/cert/prom.key
    cert_file: /var/run/kubernetes/cert/prom.crt

    kubernetes_sd_configs:

    relabel_configs:

    • source_labels: [__meta_kubernetes_role]
      action: keep
      regex: (?:apiserver|node)`

The problem happend when I don't set to apiserver

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Aug 10, 2016

Dupe of #1822

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 24, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 24, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.