Files
svcforge/deploy/chart/templates/prometheusrule.yaml
T
Nguyen Minh Phuc 50c2fe2a1e
ci / lint (push) Successful in 1m19s
ci / unit (push) Failing after 1m2s
ci / integration (push) Has been skipped
ci / types (push) Successful in 1m37s
ci / security (push) Failing after 38s
ci / dockerfile (push) Successful in 14s
ci / image (api) (push) Has been skipped
ci / image (reconciler) (push) Has been skipped
ci / image (worker) (push) Has been skipped
ci / bump (push) Has been skipped
svcforge: reference implementation
Complete working build of the system learn-python/ teaches.
164 tests, mypy --strict clean, domain coverage 99%.
2026-07-17 10:44:54 +00:00

22 lines
696 B
YAML

{{- if .Values.prometheusRule.enabled }}
{{/*
The four alerts, rendered straight from values. The rules are data, not template logic —
which is the point: an alert you want to change is a values edit and a diff, not a new
CR someone applied by hand and forgot.
Each maps to a RUNBOOK.md entry via its runbook_url annotation. An alert without a runbook
entry is a pager that teaches nothing.
*/}}
apiVersion: monitoring.coreos.com/v1
kind: PrometheusRule
metadata:
name: {{ include "svcforge.fullname" . }}
labels:
{{- include "svcforge.labels" . | nindent 4 }}
spec:
groups:
- name: svcforge
rules:
{{- toYaml .Values.prometheusRule.rules | nindent 8 }}
{{- end }}