bluewave-labs / bluewave-labs/Checkmate
Upgrade the helm chart to include a Capture daemonset to monitor cluster nodes
- Dominant language
- TypeScript
- Stars
- 10.8k
- Forks
- 1.2k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 74
Description
**Is your feature request related to a problem? Please describe.**
When I deploy capture to Kubernetes, I'd love to have each of the cluster nodes monitored immediately.
**Describe the solution you'd like**
The helm chart should include a daemonset for Capture that would be configured with just enough settings to run on the machines in the cluster in an unprivileged way.
```yaml
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: checkmate-capture
spec:
selector:
matchLabels:
component: checkmate-capture
template:
metadata:
labels:
component: checkmate-capture
spec:
containers:
- name: capture
image: ghcr.io/bluewave-labs/capture:latest
ports:
- name: metrics
containerPort: 59232
hostPort: 59232
protocol: TCP
env:
- name: PORT
value: "59232"
- name: API_SECRET
valueFrom:
secretKeyRef:
name: checkmate-secrets
key: API_SECRET
```
**Additional context**
This would come hand in hand with #2682 for an easy to use monitoring solution.
Contributor guide
Assessment
This issue has not been assessed yet.