# Default values for karma.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

replicaCount: 1

image:
  repository: ghcr.io/prymitive/karma
  tag: v0.109
  pullPolicy: IfNotPresent

nameOverride: ""
fullnameOverride: ""

# env:
# - name: ALERTMANAGER_URI
#   value: http://monitoring-prometheus-alertmanager

service:
  type: ClusterIP
  port: 80
  annotations: {}
    # prometheus.io/scrape: "true"
  labels: {}

serviceAccount:
  # Specifies whether a ServiceAccount should be created
  create: true
  # The name of the ServiceAccount to use.
  # If not set and create is true, a name is generated using the fullname template
  name:

ingress:
  enabled: true
  className: alb
  annotations:
    alb.ingress.kubernetes.io/certificate-arn: arn:aws:acm:us-west-2:557537366020:certificate/5429b3ef-e05a-4ca1-a1ce-db5d5fbe1d8d
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS": 443}]'
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/ssl-redirect: "443"
    alb.ingress.kubernetes.io/wafv2-acl-arn: arn:aws:wafv2:us-west-2:557537366020:regional/webacl/o11y-prod-global-us-west-2-gs-api/82536d62-763a-41be-b654-970ca1ea82f1
    external-dns.alpha.kubernetes.io/hostname: alertmanager.prod.aws.observability.tidbcloud.com
  path: /
  hosts:
    - alertmanager.prod.aws.observability.tidbcloud.com
  tls: []
  #  - secretName: chart-example-tls
  #    hosts:
  #      - chart-example.local

deployment:
  annotations: {}

resources:
  limits:
   cpu: "1"
   memory: 1Gi
  requests:
   cpu: 500m
   memory: 512Mi

nodeSelector: {}

tolerations: []

affinity: {}

# Labels to be added to pod
podLabels: {}

# Annotations to be added to pod
podAnnotations: {}

securityContext: {}

# configuration for liveness probe
livenessProbe:
  delay: 5
  period: 5
  path: /health

# configMap dictates if a configmap based configuration for Karma should be used
# to provide advanced configuration. NOTE, you must use port 8080!
configMap:
  enabled: true
  annotations: {}
  rawConfig:
    alertmanager:
      interval: 60s
      servers:
      - name: aws-us-east-1
        uri: https://www.ds.us-east-1.aws.observability.tidbcloud.com/internal/alerts/
        proxy: true
      - name: aws-us-west-2
        uri: https://www.ds.us-west-2.aws.observability.tidbcloud.com/internal/alerts/
        proxy: true
      - name: aws-ap-northeast-1
        uri: https://www.ds.ap-northeast-1.aws.observability.tidbcloud.com/internal/alerts/
        proxy: true
      - name: aws-ap-northeast-2
        uri: https://www.ds.ap-northeast-2.aws.observability.tidbcloud.com/internal/alerts/
        proxy: true
      - name: aws-ap-southeast-1
        uri: https://www.ds.ap-southeast-1.aws.observability.tidbcloud.com/internal/alerts/
        proxy: true
      - name: aws-ap-southeast-3
        uri: https://www.ds.ap-southeast-3.aws.observability.tidbcloud.com/internal/alerts/
        proxy: true
      - name: ap-south-1
        uri: https://www.ds.ap-south-1.aws.observability.tidbcloud.com/internal/alerts/
        proxy: true
      - name: aws-eu-central-1
        uri: https://www.ds.eu-central-1.aws.observability.tidbcloud.com/internal/alerts/
        proxy: true
      - name: gcp-asia-east1
        uri: https://www.ds.asia-east1.gcp.observability.tidbcloud.com/internal/alerts/
        proxy: true
      - name: gcp-us-central1
        uri: https://www.ds.us-central1.gcp.observability.tidbcloud.com/internal/alerts/
        proxy: true
      - name: gcp-asia-southeast1
        uri: https://www.ds.asia-southeast1.gcp.observability.tidbcloud.com/internal/alerts/
        proxy: true
      - name: gcp-asia-northeast1
        uri: https://www.ds.asia-northeast1.gcp.observability.tidbcloud.com/internal/alerts/
        proxy: true
      - name: gcp-us-west1
        uri: https://www.ds.us-west1.gcp.observability.tidbcloud.com/internal/alerts/
        proxy: true
      - name: gcp-us-east4
        uri: https://www.ds.us-east4.gcp.observability.tidbcloud.com/internal/alerts/
        proxy: true
      - name: o11y-selfmon-aws-us-east-1
        uri: https://www.ds.us-east-1.aws.observability.tidbcloud.com/internal/alerts/self-monitoring/
        proxy: true
      - name: o11y-selfmon-aws-us-west-2
        uri: https://www.ds.us-west-2.aws.observability.tidbcloud.com/internal/alerts/self-monitoring/
        proxy: true
      - name: o11y-selfmon-aws-ap-northeast-1
        uri: https://www.ds.ap-northeast-1.aws.observability.tidbcloud.com/internal/alerts/self-monitoring/
        proxy: true
      - name: o11y-selfmon-aws-ap-northeast-2
        uri: https://www.ds.ap-northeast-2.aws.observability.tidbcloud.com/internal/alerts/self-monitoring/
        proxy: true
      - name: o11y-selfmon-aws-ap-southeast-1
        uri: https://www.ds.ap-southeast-1.aws.observability.tidbcloud.com/internal/alerts/self-monitoring/
        proxy: true
      - name: o11y-selfmon-aws-ap-southeast-3
        uri: https://www.ds.ap-southeast-3.aws.observability.tidbcloud.com/internal/alerts/self-monitoring/
        proxy: true
      - name: o11y-selfmon-aws-ap-south-1
        uri: https://www.ds.ap-south-1.aws.observability.tidbcloud.com/internal/alerts/self-monitoring/
        proxy: true
      - name: o11y-selfmon-aws-eu-central-1
        uri: https://www.ds.eu-central-1.aws.observability.tidbcloud.com/internal/alerts/self-monitoring/
        proxy: true
      - name: o11y-selfmon-gcp-asia-east1
        uri: https://www.ds.asia-east1.gcp.observability.tidbcloud.com/internal/alerts/self-monitoring/
        proxy: true
      - name: o11y-selfmon-gcp-us-central1
        uri: https://www.ds.us-central1.gcp.observability.tidbcloud.com/internal/alerts/self-monitoring/
        proxy: true
      - name: o11y-selfmon-gcp-asia-southeast1
        uri: https://www.ds.asia-southeast1.gcp.observability.tidbcloud.com/internal/alerts/self-monitoring/
        proxy: true
      - name: o11y-selfmon-gcp-asia-northeast1
        uri: https://www.ds.asia-northeast1.gcp.observability.tidbcloud.com/internal/alerts/self-monitoring/
        proxy: true
      - name: o11y-selfmon-gcp-us-west1
        uri: https://www.ds.us-west1.gcp.observability.tidbcloud.com/internal/alerts/self-monitoring/
        proxy: true
      - name: o11y-selfmon-gcp-us-east4
        uri: https://www.ds.us-east4.gcp.observability.tidbcloud.com/internal/alerts/self-monitoring/
        proxy: true
      - name: o11y-selfmon-global-us-west-2
        uri: http://alertmanager-operated.self-monitoring:9093
        proxy: true
    annotations:
      default:
        hidden: false
      actions:
        - runbook_url
    history:
      enabled: false
    karma:
      name: alertmanager-unified-portal
    filters:
      default:
        - "severity=critical"
        - "@state=active"
        - "@receiver=default/observability-alertmanager-config/jiralert-prod"
    labels:
      color:
        static:
          - job
        unique:
          - cluster
          - cluster_id
          - "@receiver"
          - "@cluster"
      keep: []
      strip:
      - o11y_region
      - o11y_biz_type
    listen:
      address: "0.0.0.0"
      port: 8080
      prefix: /
    log:
      config: false
      level: info
    receivers:
      strip: []
    silenceForm:
      strip:
        labels:
          - job
    ui:
      refresh: 30s
      hideFiltersWhenIdle: true
      colorTitlebar: false
      minimalGroupWidth: 420
      alertsPerGroup: 5
      collapseGroups: collapsedOnMobile


# Names of secrets that will be mounted to `/etc/certs/<secret_name>` in the karma container.
# These secrets can be used to configure TLS for Karma's Alertmanagers by passing their paths to
# the appropriate Karma configuration parameters. For example, secret `foo` containing a `ca.crt`
# will yield a file at `/etc/certs/foo/ca.crt`. That path can then be provided as the value to
# `configMap.rawConfig.alertmanager.servers[].tls.ca`.
# See <https://github.com/prymitive/karma/blob/master/docs/CONFIGURATION.md#alertmanagers>.
certSecretNames: []
