[distributions/gateway] add gateway distribution #845
Conversation
There was a problem hiding this comment.
i still don't quite get why such a distribution is needed. couldn't this be handled by a user-owned config.yaml and otelcol-contrib? albeit with a bigger footprint of course with more components. Also, I think this kind of conflicts with the gateway deployment pattern described in the docs.
some other points:
- please adjust the goreleaser configure.go file so that i generates your intended goreleaser.yaml config
- please add the new distro to the pipeline configs under .github/workflows
There was a problem hiding this comment.
you don't need to split the goreleaser files. that is only necessary for otelcol-contrib for nightly testing purposes, but this will be handled by configure.go anyways when you change it
|
We talked about this during the SIG Collector, and we seem to agree that the name "gateway" does not match what we have in the manifest here. The need for this specific distribution isn't also either very clear. |
Co-authored-by: Moritz Wiesinger <moritz.wiesinger@dynatrace.com>
Co-authored-by: Moritz Wiesinger <moritz.wiesinger@dynatrace.com>
This is a new distribution that targets the use case of deploying the collector as a gateway.
In this scenario, the collector is completely passive and listens for traffic in various protocols, and exports to OTLP.
More information in the README of the distribution for review.
Fixes #834