Skip to content

Commit

Permalink
chore(alerts) debug test
Browse files Browse the repository at this point in the history
  • Loading branch information
ibakshay committed Sep 19, 2024
1 parent 31d7305 commit 823c467
Showing 1 changed file with 0 additions and 212 deletions.
212 changes: 0 additions & 212 deletions alerts/ci/test-values.yaml
Original file line number Diff line number Diff line change
@@ -1,225 +1,13 @@
# SPDX-FileCopyrightText: 2024 SAP SE or an SAP affiliate company and Greenhouse contributors
# SPDX-License-Identifier: Apache-2.0

global:
## common labels to apply to all resources
##
commonLabels: {}

# kube-prometheus-stack configuration scoped to alerts
alerts:

## Create default rules for monitoring the cluster
##
defaultRules:
create: true
rules:
alertmanager: true
etcd: false
configReloaders: false
general: false
k8sContainerCpuUsageSecondsTotal: false
k8sContainerMemoryCache: false
k8sContainerMemoryRss: false
k8sContainerMemorySwap: false
k8sContainerResource: false
k8sPodOwner: false
kubeApiserverAvailability: false
kubeApiserverBurnrate: false
kubeApiserverHistogram: false
kubeApiserverSlos: false
kubeControllerManager: false
kubelet: false
kubeProxy: false
kubePrometheusGeneral: false
kubePrometheusNodeRecording: false
kubernetesApps: false
kubernetesResources: false
kubernetesStorage: false
kubernetesSystem: false
kubeSchedulerAlerting: false
kubeSchedulerRecording: false
kubeStateMetrics: false
network: false
node: false
nodeExporterAlerting: false
nodeExporterRecording: false
prometheus: false
prometheusOperator: false
windows: false

## Flag to disable all the kubernetes component scrapers
##
kubernetesServiceMonitors:
enabled: false

## Setting to true produces cleaner resource names, but requires a data migration because the name of the persistent volume changes. Therefore this should only be set once on initial installation.
##
cleanPrometheusOperatorObjectNames: true

## Install Prometheus Operator CRDs
##
crds:
enabled: true

windowsMonitoring:
## Deploys the windows-exporter and Windows-specific dashboards and rules (job name must be 'windows-exporter')
enabled: false

## Using default values from https://github.com/grafana/helm-charts/blob/main/charts/grafana/values.yaml
##
grafana:
enabled: false

## Configuration for thanosRuler
## ref: https://thanos.io/tip/components/rule.md/
##
thanosRuler:

## Deploy thanosRuler
##
enabled: false


## Configuration for the Prometheus instance
##
prometheus:

## Deploy Prometheus
##
enabled: false

## Deploy node exporter as a daemonset to all nodes
##
nodeExporter:
## Deploy prometheus node-exporter
##
enabled: false

## Component scraping kube state metrics
##
kubeStateMetrics:
## Deploy kube-state-metrics subchart
enabled: false

## Manages Prometheus and Alertmanager components
##
prometheusOperator:
## Deploy prometheus-operator
enabled: true

## Configuration for alertmanager
## ref: https://prometheus.io/docs/alerting/alertmanager/
##
alertmanager:

## Deploy alertmanager
##
enabled: true

## Alertmanager configuration directives
## ref: https://prometheus.io/docs/alerting/configuration/#configuration-file
## https://prometheus.io/webtools/alerting/routing-tree-editor/
##
config:
global:
resolve_timeout: 5m
inhibit_rules:
- source_matchers:
- 'severity = critical'
target_matchers:
- 'severity =~ warning|info'
equal:
- 'namespace'
- 'alertname'
- source_matchers:
- 'severity = warning'
target_matchers:
- 'severity = info'
equal:
- 'namespace'
- 'alertname'
- source_matchers:
- 'alertname = InfoInhibitor'
target_matchers:
- 'severity = info'
equal:
- 'namespace'
route:
group_by:
- organization
- alertname
- cluster
- region
group_wait: 30s
group_interval: 5m
repeat_interval: 12h
continue: false
receiver: 'null'
routes:
- matchers:
- alertname =~ "Watchdog|InfoInhibitor"
receiver: "null"
continue: false

receivers:
- name: 'null'

templates:
- '/etc/alertmanager/config/*.tmpl'
- '/etc/alertmanager/notification-templates/*.tmpl'


ingress:
enabled: true
hosts:
- dummy-host

## By default, a ca-bundle is deployed to enable tls between Prometheus and Alertmanager
annotations:
disco: "true"
kubernetes.io/tls-acme: "true"
nginx.ingress.kubernetes.io/auth-tls-secret: "{{ $.Release.Namespace }}/{{ $.Release.Namespace }}-ca-bundle"
nginx.ingress.kubernetes.io/auth-tls-verify-client: "true"
nginx.ingress.kubernetes.io/auth-tls-verify-depth: "3"
nginx.ingress.kubernetes.io/cors-allow-headers: Content-Type
nginx.ingress.kubernetes.io/cors-allow-methods: DELETE
nginx.ingress.kubernetes.io/enable-cors: "true"
ingressClassName: nginx

## Settings affecting alertmanagerSpec
## ref: https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md#alertmanagerspec

alertmanagerSpec:

## Defines the strategy used by AlertmanagerConfig objects to match alerts.
##
alertmanagerConfigMatcherStrategy:
type: OnNamespace

## AlertmanagerConfigs to be selected to merge and configure Alertmanager with.
##
alertmanagerConfigSelector:
matchLabels:
plugin: "{{ $.Release.Name }}"

## Additional volumes on the output StatefulSet definition.
volumeMounts:
- mountPath: /etc/alertmanager/notification-templates
name: alertmanager-notification-templates
readOnly: true

## Additional VolumeMounts on the output StatefulSet definition.
volumes:
- configMap:
name: alertmanager-notification-templates
name: alertmanager-notification-templates


testFramework:
enabled: true
image:
registry: ghcr.io
repository: cloudoperators/greenhouse-extensions-integration-test
tag: main
imagePullPolicy: IfNotPresent

0 comments on commit 823c467

Please sign in to comment.