Berserk Admin
Cluster management, Helm charts, Kubernetes, and meta service configuration
Administration documentation for deploying and managing Berserk clusters. For initial installation, see the Quick Start.
Services
Berserk is composed of the following services:
| Service | Description | Default Port |
|---|---|---|
| meta | Metadata management | 9500 |
| query | Query engine | 9510 |
| ingest | Telemetry ingestion (OTLP) | 4317 (gRPC) / 4318 (HTTP) |
| janitor | Background maintenance (merging, compaction) | — |
| nursery | Baby segment management | 9530 |
| ui | Web interface | 80 |
Helm Configuration
The Berserk Helm chart is available at:
helm repo add berserk https://berserkdb.github.io/helm-chartsKey Parameters
| Parameter | Description | Default |
|---|---|---|
global.imageTag | Image tag for all services | Chart appVersion |
global.storage.endpoint | S3-compatible storage endpoint | "" |
global.storage.bucket | S3 bucket name | "" |
global.storage.region | S3 region | "auto" |
global.observability.otlpEnabled | Enable OTLP telemetry export | false |
global.observability.otlpEndpoint | OTLP collector endpoint | "ingest:4317" |
global.s3Credentials.secretName | Name of the S3 credentials secret | "s3-credentials" |
global.postgresCredentials.secretName | Name of the Postgres credentials secret | "postgres-credentials" |
query.cache.size | Query segment cache size | "128Gi" |
ingest.service.ports.otlpGrpc | OTLP gRPC ingestion port | 4317 |
ingest.service.ports.otlpHttp | OTLP HTTP ingestion port | 4318 |
janitor.config.mergerIntervalSeconds | Interval between merge operations | 300 |
See the helm-charts repository for full configuration reference and example values.
Observability
Berserk services emit their own logs, metrics, and traces via OpenTelemetry. You can export this telemetry to any OTLP-compatible endpoint — including Berserk itself — for monitoring the health of your cluster.
Enable it in your Helm values:
global:
observability:
otlpEnabled: true
otlpEndpoint: "your-collector:4317"When enabled, all Berserk services (meta, query, ingest, janitor, nursery) will send telemetry to the configured endpoint over gRPC. This is useful for debugging query performance, tracking ingestion throughput, and alerting on service health.