https://github.com/kevinetore/helm-signal-alertmanager
Helm wrapper for alertmanager-webhook-signal and signal-cli-rest-api
https://github.com/kevinetore/helm-signal-alertmanager
alertmanager-webhook-signal signal-cli-rest-api
Last synced: 4 months ago
JSON representation
Helm wrapper for alertmanager-webhook-signal and signal-cli-rest-api
- Host: GitHub
- URL: https://github.com/kevinetore/helm-signal-alertmanager
- Owner: kevinetore
- Created: 2025-10-03T10:31:10.000Z (8 months ago)
- Default Branch: main
- Last Pushed: 2025-10-06T18:53:15.000Z (8 months ago)
- Last Synced: 2025-10-22T06:47:05.036Z (8 months ago)
- Topics: alertmanager-webhook-signal, signal-cli-rest-api
- Language: Smarty
- Homepage:
- Size: 4.88 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Alertmanager Signal Helm Chart
This Helm chart deploys Alertmanager Webhook to Signal integration using two main components:
1. Signal CLI REST API: Runs a Signal client in a container and handles sending messages.
2. Alertmanager Webhook (alertmanager-webhook-signal): Receives alerts from Prometheus Alertmanager and forwards them to Signal via the Signal CLI REST API.
## Usage
### After deploying the chart:
Get the QR code to link your Signal device:
kubectl logs -f alertmanager-signal- -c webhook
Scan the QR code with your Signal app to link your number with the signal-cli container.
The webhook listens on port 10000.
#### Managing Groups
If you want to send messages to a Signal group, after scanning the QR code you should run the following commands:
```bash
kubectl exec -it alertmanager-signal- -c signal-cli -- bash
curl -X 'GET' \
'http://localhost:8080/v1/groups/' \
-H 'accept: application/json'
```
Use the Id field from the output in your webhook configuration under recipients:
recipients:
- "group."
#### Verify Alerts:
Alerts sent by Prometheus should now appear as Signal messages for the configured recipients.
### Openshift
ServiceAccount and SCC Requirements:
On OpenShift, the Signal CLI REST API container runs as UID 1000. Openshift which will prevent the pod from starting unless the container is allowed to run as this UID.
Grant anyuid to the ServiceAccount:
Before deploying the chart, create the ServiceAccount and grant it the anyuid SCC:
```bash
oc adm policy add-scc-to-user anyuid -z alertmanager-signal-sa -n
```