hanahmily opened a new pull request, #68:
URL: https://github.com/apache/skywalking-banyandb-helm/pull/68
This PR adds Helm chart support for deploying BanyanDB data nodes with
trace-pipeline sampler plugins enabled.
### What's added
- \`plugins.enabled\`, \`plugins.image\`, \`plugins.mountMode\`,
\`plugins.initContainer\`, and \`plugins.thirdParty\` values.
- Helper templates for the plugin host image, carrier image, third-party
image, and configuration validation.
- Data-node StatefulSet wiring:
- Use the \`-plugins\` host image when plugins are enabled.
- Mount the carrier image via initContainer+emptyDir (default) or OCI
imageVolume.
- Pass \`--trace-pipeline-native-plugin-enabled=true\` and
\`--trace-pipeline-trusted-plugin-dir=/plugins\` to data nodes.
- Optional third-party plugin initContainer mounted at
\`/plugins/thirdparty\`.
- \`validate-plugins.yaml\` to fail fast on mis-configuration (e.g.
standalone mode, missing image tag, invalid mountMode).
### Verification
- Rendered the chart with \`plugins.enabled=true\` and confirmed the data
node gets the plugin image, init container, flags, and volumes.
- Verified on a local kind cluster running the BanyanDB head image that
after updating a trace group with a sampler pipeline, the data node loads the
plugin and \`banyandb_trace_pipeline_sampler_active_count{group=...}\` reports
1.
- The branch is rebased on master and includes the name-length validation
from #67.
Relates to
https://github.com/apache/skywalking-banyandb/blob/main/docs/operation/plugins.md
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
