From b4d2d69f263dd6471ae6dd0a7a4412d545c4ab41 Mon Sep 17 00:00:00 2001 From: Jeff Billimek Date: Tue, 10 Nov 2020 08:31:00 -0500 Subject: [PATCH] removing endpoints for controller and scheduler ... After upgrading to k3s 1.19 (from 1.18), the promethgeus target scraping for those two targets stopped wokring, `Get "http://10.2.0.30:10252/metrics": dial tcp 10.2.0.30:10252: connect: connection refused` Looking at https://github.com/rancher/k3s/issues/425#issuecomment-672019664 suggests the endpoint approach should work. Experimenting with removing the explicit endpoint callout to see if there is an improvement. Signed-off-by: Jeff Billimek --- .../kube-prometheus-stack/kube-prometheus-stack.yaml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/monitoring/kube-prometheus-stack/kube-prometheus-stack.yaml b/monitoring/kube-prometheus-stack/kube-prometheus-stack.yaml index 624aa7302c9..15653925653 100644 --- a/monitoring/kube-prometheus-stack/kube-prometheus-stack.yaml +++ b/monitoring/kube-prometheus-stack/kube-prometheus-stack.yaml @@ -320,12 +320,12 @@ spec: enabled: false kubeControllerManager: enabled: true - endpoints: - - 10.2.0.30 + # endpoints: + # - 10.2.0.30 kubeScheduler: enabled: true - endpoints: - - 10.2.0.30 + # endpoints: + # - 10.2.0.30 kubeProxy: enabled: false prometheus-node-exporter: