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

bug: multiple metrics not scrapeable #1894

Open
steled opened this issue Dec 22, 2024 · 2 comments
Open

bug: multiple metrics not scrapeable #1894

steled opened this issue Dec 22, 2024 · 2 comments

Comments

@steled
Copy link

steled commented Dec 22, 2024

Chart name and version
chart: victoria-metrics-k8s-stack
version: 0.33.0

Describe the bug
I'm not able to scrape:

  • kube-controller-manager (connect: connection refused)
  • kube-etcd (tls: failed to verify certificate: x509: certificate signed by unknown authority)
  • kube-proxy (connect: connection refused)
  • kube-scheduler (connect: connection refused)

I checked the bind-address of scheduler and controller and they are set to 127.0.0.1 so they are only listening on them:

$ netstat -tulpn | grep "10259\|10257"
(No info could be read for "-p": geteuid()=500 but you should be root.)
tcp        0      0 127.0.0.1:10259         0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.1:10257         0.0.0.0:*               LISTEN      -

How can I configure them to use in cluster communication like kube-apiserver scrape?

@AndrewChubatiuk
Copy link
Collaborator

hey @steled
are you using k3s?

@steled
Copy link
Author

steled commented Dec 23, 2024

Hi @AndrewChubatiuk,
no I'm using plain Kubernetes in version 1.31.4 installed via kubeone

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

2 participants