dos4dev/kube
1
0
Fork 0
forked from k-space/kube
Code Pull Requests Activity

Consolidate monitoring stack to Kube master nodes

Browse Source
This commit is contained in:
Lauri Võsandi
2024-08-23 07:58:26 +03:00
parent 18483197c9
commit 67fb6c3727
7 changed files with 28 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
monitoring/README.md
View File

@@ -5,10 +5,10 @@ and the corresponding AlertManager is accessible at [am.k-space.ee](https://am.k
Both are [deployed by ArgoCD](https://argocd.k-space.ee/applications/monitoring)
from this Git repo directory using Prometheus operator.
Note that Prometheus and other monitoring stack components should use the
`dedicated: monitoring` Kubernetes node selector to make sure the components
get scheduled on `mon[1-3]` nodes which are hosted in a privileged VLAN where
they have access to UPS SNMP targets, Mikrotik router/switch API-s etc.
Note that Prometheus and other monitoring stack components should appropriate
node selector to make sure the components get scheduled on nodes which are
hosted in a privileged VLAN where they have access to UPS SNMP targets,
Mikrotik router/switch API-s etc.
To add monitoring targets inside the Kubernetes cluster make use of
[PodMonitor](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/getting-started.md#using-podmonitors) or ServiceMonitor custom