Merge pull request #214 from k8s-at-home/alertmanager-bot-common

[alertmanager-bot] new chart
This commit is contained in:
Ryan Holt 2020-11-24 19:05:10 -05:00 committed by GitHub
commit 8d6ec42996
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
8 changed files with 149 additions and 0 deletions

View File

@ -0,0 +1,24 @@
# Patterns to ignore when building packages.
# This supports shell glob matching, relative path matching, and
# negation (prefixed with !). Only one pattern per line.
.DS_Store
# Common VCS dirs
.git/
.gitignore
.bzr/
.bzrignore
.hg/
.hgignore
.svn/
# Common backup files
*.swp
*.bak
*.tmp
*~
# Various IDEs
.project
.idea/
*.tmproj
.vscode/
# OWNERS file for Kubernetes
OWNERS

View File

@ -0,0 +1,21 @@
apiVersion: v2
appVersion: 0.4.2
description: Bot for Prometheus Alertmanager
name: alertmanager-bot
version: 1.0.0
keywords:
- alertmanager
- telegram
- bot
- alerting
home: https://github.com/k8s-at-home/charts/tree/master/charts/alertmanager-bot
sources:
- https://hub.docker.com/r/metalmatze/alertmanager-bot
- https://github.com/metalmatze/alertmanager-bot
maintainers:
- name: billimek
email: jeff@billimek.com
dependencies:
- name: common
repository: https://k8s-at-home.com/charts/
version: 1.6.1

View File

@ -0,0 +1,8 @@
approvers:
- billimek
- onedr0p
- bjw-s
reviewers:
- billimek
- onedr0p
- bjw-s

View File

@ -0,0 +1,61 @@
# alertmanager-bot
This is a helm chart for [alertmanager-bot](https://github.com/metalmatze/alertmanager-bot).
**This chart is not maintained by the upstream project and any issues with the chart should be raised [here](https://github.com/k8s-at-home/charts/issues/new/choose)**
## TL;DR;
```shell
$ helm repo add k8s-at-home https://k8s-at-home.com/charts/
$ helm install k8s-at-home/alertmanager-bot
```
## Installing the Chart
To install the chart with the release name `my-release`:
```console
helm install --name my-release k8s-at-home/alertmanager-bot
```
## Uninstalling the Chart
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release --purge
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
## Configuration
Read through the charts [values.yaml](https://github.com/k8s-at-home/charts/blob/master/charts/alertmanager-bot/values.yaml)
file. It has several commented out suggested values.
Additionally you can take a look at the common library [values.yaml](https://github.com/k8s-at-home/charts/blob/master/charts/common/values.yaml) for more (advanced) configuration options.
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install alertmanager-bot \
--set env.TZ="America/New_York" \
k8s-at-home/alertmanager-bot
```
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the
chart. For example,
```console
helm install alertmanager-bot k8s-at-home/alertmanager-bot --values values.yaml
```
```yaml
image:
tag: ...
```
---
**NOTE**
If you get
```console
Error: rendered manifests contain a resource that already exists. Unable to continue with install: existing resource conflict: ...`
```
it may be because you uninstalled the chart with `skipuninstall` enabled, you need to manually delete the pvc or use `existingClaim`.

View File

@ -0,0 +1,7 @@
service:
enabled: false
probes:
liveness:
enabled: false
readiness:
enabled: false

View File

@ -0,0 +1 @@
{{- include "common.notes.defaultNotes" . -}}

View File

@ -0,0 +1 @@
{{ include "common.all" . }}

View File

@ -0,0 +1,26 @@
# Default values for alertmanager-bot.
image:
repository: metalmatze/alertmanager-bot
pullPolicy: IfNotPresent
tag: 0.4.2
strategy:
type: Recreate
# See more environment varaibles in the alertmanager-botdocumentation
# https://github.com/metalmatze/alertmanager-bot
env:
STORE: bolt
BOLT_PATH: /data/bot.db
# ALERTMANAGER_URL:
# TELEGRAM_ADMIN:
# TELEGRAM_TOKEN:
service:
enabled: false
persistence:
data:
enabled: false
emptyDir: false