-
Notifications
You must be signed in to change notification settings - Fork 293
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
[wip] node-exporter connector #2964
Conversation
@Azure/aks-pm issue needs labels |
15 similar comments
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@shanalily you still want this PR? |
@Azure/aks-pm issue needs labels |
9 similar comments
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
11 similar comments
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
Closing as this is being released |
Creating a PR now so I can share a way to scrape node-exporter on AKS node VM with kube-prometheus.
prometheus-operator needs there to be endpoints so it can use the 'endpoints' service discovery role for ServiceMonitors. For kubelet, it creates and reconciles kubelet endpoints and service instead of using the node service discovery role, so that's what the daemonset here is doing.
I still need to clean this up if I want to override the node-exporter k8s daemonset config.