We are trying to break away the config from the values file (and implement config namespacing), because having a file with 2k LOC (we are going to have a lot of transforms) seems rather far away from being ideal and also prevents us from validating and testing the config ahead of release.
Alas, existingConfigMaps seems to conflicts with the use of extraVolumes and extraVolumeMounts in the StatefulSet specs.
Are we missing something to make the setup work, or does the chart currently not handle this scenario ?
Version
0.33.0
File layout
⇒ tree config
config
├── sinks
│  ├── datadog_logs.yaml
│  ├── datadog_metrics.yaml
│  ├── datadog_traces.yaml
│  └── stdout.yaml
├── sources
│  ├── datadog_agents.yaml
│  ├── vector_logs.yaml
│  └── vector_metrics.yaml
├── tests
├── transforms
│  ├── datadog_logs_vector_as_sender.yaml
│  ├── datadog_traces_vector_as_sender.yaml
│  ├── vector_logs_clean.yaml
│  ├── vector_metrics_limit_cardinalities.yaml
│  └── vector_metrics_router.yaml
└── vector.yaml
Hi 👋
We are trying to break away the config from the values file (and implement config namespacing), because having a file with 2k LOC (we are going to have a lot of transforms) seems rather far away from being ideal and also prevents us from validating and testing the config ahead of release.
Alas,
existingConfigMaps
seems to conflicts with the use ofextraVolumes
andextraVolumeMounts
in the StatefulSet specs.First, it is required to escape the automagically built config, then the values provided in
extraVolumeMounts
seems either ignored or overridden by the current logic incharts/vector/templates/_pod.tpl
: https://github.com/vectordotdev/helm-charts/blob/72ffb20576cf4141b6881ada2660fdaadf2e22ad/charts/vector/templates/_pod.tpl#L186-L192Are we missing something to make the setup work, or does the chart currently not handle this scenario ?
Version
0.33.0
File layout
Validating the config
Our configmap
Values file
Generated
StatefulSet
resource