2f302943fe
In some cases we have been using `alert-rules` in some cases `prometheus-rulefiles`. This led to confusion [1]. Instead, unify the Prometheus rules configmap labels to: ```yaml labels: role: alert-rules ``` [1] https://github.com/coreos/prometheus-operator/issues/1102
30 lines
742 B
YAML
30 lines
742 B
YAML
apiVersion: monitoring.coreos.com/v1
|
|
kind: Prometheus
|
|
metadata:
|
|
name: k8s
|
|
labels:
|
|
prometheus: k8s
|
|
spec:
|
|
replicas: 2
|
|
version: v2.2.1
|
|
serviceAccountName: prometheus-k8s
|
|
serviceMonitorSelector:
|
|
matchExpressions:
|
|
- {key: k8s-app, operator: Exists}
|
|
ruleSelector:
|
|
matchLabels:
|
|
role: alert-rules
|
|
prometheus: k8s
|
|
resources:
|
|
requests:
|
|
# 2Gi is default, but won't schedule if you don't have a node with >2Gi
|
|
# memory. Modify based on your target and time-series count for
|
|
# production use. This value is mainly meant for demonstration/testing
|
|
# purposes.
|
|
memory: 400Mi
|
|
alerting:
|
|
alertmanagers:
|
|
- namespace: monitoring
|
|
name: alertmanager-main
|
|
port: web
|