* add new ebpf-profiler distribution
* add changelog entry
* mark ebpf-profiler as a valid component
* only release on amd for now
* enable cgo
* don't rely on scratch image
* use a custom config file for profiler
* run tests with profiles feature flags
* run ebpf container privileged
* run container as root
* mount debugfs?
* add dash to org name
* add ebpf-profiler exception for components to include
* it's connector and extensions that must facilitate collection and processing
* Update distributions/otelcol-ebpf-profiler/README.md
Co-authored-by: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com>
* Update .github/workflows/release-ebpf-profiler.yaml
Co-authored-by: Christos Kalkanis <christos.kalkanis@elastic.co>
* add arm64
* remove unneeded name
* Update .github/workflows/ci-goreleaser-ebpf-profiler.yaml
Co-authored-by: Florian Lehner <florianl@users.noreply.github.com>
* add extension to config_file parameter
* move the config option to be after all the docker ones
* remove arm64
* use custom ld flags
* add custom go tags
* only keep the extldflags ldflag
* remove unneeded arm version
* document the need for cgo
* don't release ebpf images yet
* refine cgo doc
* remove arm64 from goreleaser
* add glibc version requirement
---------
Co-authored-by: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com>
Co-authored-by: Christos Kalkanis <christos.kalkanis@elastic.co>
Co-authored-by: Moritz Wiesinger <moritz.wiesinger@dynatrace.com>
Co-authored-by: Florian Lehner <florianl@users.noreply.github.com>
Verify that all components declared in manifest.yaml files are defined in the builder-config.yaml from the opentelemetry-collector-contrib repository, ensuring they were built and tested successfully.
Damien Mathieu