svcforge: reference implementation
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
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
Complete working build of the system learn-python/ teaches. 164 tests, mypy --strict clean, domain coverage 99%.
This commit is contained in:
@@ -0,0 +1,21 @@
|
||||
{{- 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 }}
|
||||
Reference in New Issue
Block a user