adjustments based on k3s-io/k3s#3619 (comment)

tuxpeople · Mar 29, 2022 · 918e515 · 918e515
1 parent ef1ba73
commit 918e515
Show file tree

Hide file tree

Showing 2 changed files with 16 additions and 2 deletions.
diff --git a/cluster/apps/monitoring/kube-prometheus-stack/helm-release.yaml b/cluster/apps/monitoring/kube-prometheus-stack/helm-release.yaml
@@ -179,12 +179,28 @@ spec:
         - 192.168.8.201
         - 192.168.8.202
         - 192.168.8.203
+      service:
+        enabled: true
+        port: 10259
+        targetPort: 10259
+      serviceMonitor:
+        enabled: true
+        https: true
+        insecureSkipVerify: true
     kubeScheduler:
       enabled: true
       endpoints:
         - 192.168.8.201
         - 192.168.8.202
         - 192.168.8.203
+      service:
+        enabled: true
+        port: 10257
+        targetPort: 10257
+      serviceMonitor:
+        enabled: true
+        https: true
+        insecureSkipVerify: true
     kubeProxy:
       enabled: true
       endpoints:

diff --git a/provision/ansible/inventory/group_vars/master/k3s.yml b/provision/ansible/inventory/group_vars/master/k3s.yml
@@ -48,7 +48,6 @@ k3s_server:
   #   - "allocate-node-cidrs"
     # Required to monitor component with kube-prometheus-stack
   kube-controller-manager-arg:
-    - "address=0.0.0.0"
     - "bind-address=0.0.0.0"
   kube-proxy-arg:
     # # Various
@@ -64,7 +63,6 @@ k3s_server:
     # - "feature-gates=MixedProtocolLBService=true"
     # - "feature-gates=ReadWriteOncePod=true"
     # Required to monitor component with kube-prometheus-stack
-    - "address=0.0.0.0"
     - "bind-address=0.0.0.0"
   # Required to monitor etcd with kube-prometheus-stack
   etcd-expose-metrics: true