Kubernetes deployment
Run reveald as a DaemonSet to collect logs from every node in your cluster. This is ideal for collecting CRI container logs, journald entries, and host-level log files.
DaemonSet manifest
Secret for webhook URL
Don't put your webhook URL in the ConfigMap. Use a Kubernetes Secret and reference it via secretKeyRef as shown above.
Collecting journald in Kubernetes
To collect journald alongside container logs, mount the journal directories:
And add a journald source to your config:
Resource recommendations
| Cluster size | CPU request | Memory request | CPU limit | Memory limit |
|---|---|---|---|---|
| Small (< 50 pods/node) | 50m | 64Mi | 200m | 256Mi |
| Medium (50-200 pods/node) | 100m | 128Mi | 500m | 512Mi |
| Large (> 200 pods/node) | 200m | 256Mi | 1000m | 1Gi |
Adjust based on log volume. Monitor memory usage and increase limits if reveald is OOM-killed.