You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replace my-data-prepper-release with your desired release name.
36
+
Replace my-data-prepper-release with your desired release name. When no explicit pipeline is defined, this will configure a demo pipeline using a random source and stdout sink.
37
37
38
38
## Configuration
39
39
40
40
The Data Prepper Helm chart comes with a variety of configuration options to tailor the deployment to your needs.
41
-
The default values are specified in the [values.yaml](values.yaml) file. You can override these values by providing your own values.yaml file during installation or by specifying configuration options with --set flags.
41
+
The default values are specified in the [values.yaml](values.yaml) file. You can override these values by providing your own `values.yaml` file during installation or by specifying configuration options with --set flags.
42
42
43
43
For a detailed list of configuration options, refer to the values.yaml file or the [Data Prepper documentation](https://opensearch.org/docs/latest/data-prepper/managing-data-prepper/configuring-data-prepper/).
| pipelineConfig.existingSecret | string |`""`| The name of the existing secret containing the pipeline configuration. If enabled is false existingSecret is used. The existingSecret must have a key named `pipelines.yaml`. |
| pipelineConfig.enabled | boolean |`false`| Enable inline configuration in `config` sub key. |
104
+
| pipelineConfig.config | object |`{}`| Pipeline configuration file inline if `enabled` is set to true |
105
+
| pipelineConfig.demoPipeline | boolean | "" | If set, a demo pipeline will be provisioned with source `random` and sink `stdout`. |
106
+
| pipelineConfig.existingSecret | string |`""`| The name of an existing secret containing the pipeline configuration. If enabled is false existingSecret is used. The existingSecret must have a key named `pipelines.yaml`. |
Copy file name to clipboardExpand all lines: charts/data-prepper/templates/deployment.yaml
+4-2Lines changed: 4 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -90,10 +90,12 @@ spec:
90
90
name: {{ include "data-prepper.fullname" . }}-config
91
91
- name: data-prepper-pipelines
92
92
secret:
93
-
{{- if .Values.pipelineConfig.enabled }}
93
+
{{- if eq "true" (include "data-prepper.demoPipeline" .) }}
94
+
secretName: {{ include "data-prepper.fullname" . }}-demo-pipeline
95
+
{{- else if .Values.pipelineConfig.enabled }}
94
96
secretName: {{ include "data-prepper.fullname" . }}-pipeline
95
97
{{- else }}
96
-
secretName: {{ required "A valid .Values.pipelineConfig.existingSecret entry required!" .Values.pipelineConfig.existingSecret }}
98
+
secretName: {{ required "A valid pipeline configuration is required! Please set one of:\npipelineConfig.existingSecret - for your custom pipeline secret\npipelineConfig.enabled - for inline configuration in values.yaml or\npipelineConfig.demoPipeline=true - for a sample demo pipeline using random source and stdout sink." .Values.pipelineConfig.existingSecret }}
0 commit comments