9ed63f191f
For `--dry-run` to work with kubectl a Kubernetes cluster's apiserver is actually used, which is unnecessary for generating these manifests. This approach also allows further customization, such as adding labels to the generated manifests.
29 lines
720 B
YAML
29 lines
720 B
YAML
apiVersion: monitoring.coreos.com/v1alpha1
|
|
kind: Prometheus
|
|
metadata:
|
|
name: k8s
|
|
labels:
|
|
prometheus: k8s
|
|
spec:
|
|
replicas: 2
|
|
version: v1.5.2
|
|
serviceMonitorSelector:
|
|
matchExpression:
|
|
- {key: k8s-apps, operator: Exists}
|
|
ruleSelector:
|
|
matchLabels:
|
|
role: prometheus-rulefiles
|
|
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
|