Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/redpanda-data/redpanda-connect-helm-chart
Helm 3 repository for benthosdev/benthos
https://github.com/redpanda-data/redpanda-connect-helm-chart
benthos go golang helm kubernetes
Last synced: about 2 months ago
JSON representation
Helm 3 repository for benthosdev/benthos
- Host: GitHub
- URL: https://github.com/redpanda-data/redpanda-connect-helm-chart
- Owner: redpanda-data
- License: mit
- Created: 2021-11-02T04:51:06.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2024-05-24T22:47:46.000Z (4 months ago)
- Last Synced: 2024-06-09T16:40:32.873Z (3 months ago)
- Topics: benthos, go, golang, helm, kubernetes
- Language: Smarty
- Homepage:
- Size: 418 KB
- Stars: 30
- Watchers: 5
- Forks: 22
- Open Issues: 8
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
- awesome-golang-repositories - benthos-helm-chart
README
# benthos-helm-chart
Benthos Helm Chart.
Benthos 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 Benthos instance in either streams mode or standalone.
## Installation
```bash
helm repo add benthos https://benthosdev.github.io/charts/
helm repo update
helm install benthos/benthos
```
## Configuration
The config parameter should contain the configuration as it would be parsed by the Benthos binary.
```yaml
# values.yaml
config:
input:
label: "no_config_in"
generate:
mapping: root = "This Benthos 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](./values.yaml). You should refer to the [upstream Benthos documentation](https://www.benthos.dev/docs/configuration/about) for the configuration of your pipeline.
## Streams mode
When running Benthos in [streams mode](https://www.benthos.dev/docs/guides/streams_mode/about), all individual stream configuration files should be combined and placed in a single Kubernetes `ConfigMap`, like so:
```yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: benthos-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.
```yaml
# values.yaml
streams:
enabled: true
streamsConfigMap: "benthos-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 Benthos 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 Benthos configuration syntax.
```yaml
metrics:
prometheus: {}
tracing:
openTelemetry:
http: []
grpc: []
tags: {}
logger:
level: INFO
static_fields:
'@service': benthos
```