bento-helm-chart

Bento Helm Chart.

Bento is a high performance and resilient stream processor, able to connect various sources and sinks in a range of brokering patterns and perform hydration, enrichments, transformations and filters on payloads.

This Helm Chart deploys a single Bento instance in either streams mode or standalone.

Installation

helm repo add bento-helm https://warpstreamlabs.github.io/bento-helm-chart
helm repo update
helm install bento bento-helm/bento
# OR
helm upgrade --install bento oci://ghcr.io/warpstreamlabs/bento-helm/bento --version 0.1.0

Configuration

The config parameter should contain the configuration as it would be parsed by the Bento binary.

# values.yaml
config:
  input:
    label: "no_config_in"
    generate:
      mapping: root = "This Bento instance is unconfigured!"
      interval: 1m
  output:
    label: "no_config_out"
    stdout:
      codec: lines

The full list of available configuration for the Helm Chart can be found in the values.yaml file. You should refer to the upstream Bento documentation for the configuration of your pipeline.

Streams mode

When running Bento in streams mode, all individual stream configuration files should be combined and placed in a single Kubernetes ConfigMap, like so:

apiVersion: v1
kind: ConfigMap
metadata:
  name: bento-streams
data:
  hello.yaml: |
    input:
      generate:
        mapping: root = "woof"
        interval: 5s
        count: 0
    output:
      stdout:
        codec: lines
  aaaaa.yaml: |
    input:
      generate:
        mapping: root = "meow"
        interval: 2s
        count: 0
    output:
      stdout:
        codec: lines

Then you can simply reference your ConfigMap and enable streams mode in your values.yaml file.

# values.yaml
streams:
  enabled: true
  streamsConfigMap: "bento-streams"

Currently the streams mode ConfigMap should be applied separately from and before installation of the helm chart; support for deploying additional ConfigMap's within the chart may be implemented later.

Global Configuration

When deploying Bento in streams mode, you may want to configure global tracing, logging and http configuration which is shared across all of your pipelines.

This can be done by specifying configuration under the metrics, logger and tracing configuration sections in your values.yaml file. These all use their respective upstream Bento configuration syntax.

metrics:
  prometheus: {}

tracing:
  openTelemetry:
    http: []
    grpc: []
    tags: {}

logger:
  level: INFO
  static_fields:
    '@service': bento