Skip to content

nr-ebpf-agent ipv6 too many colons in address #2014

@pauljohnston-entrata

Description

@pauljohnston-entrata

Bug description

nr-ebpf-agent

otel collector ds doesn't work on an ipv6 only cluster.

Version of Helm and Kubernetes

3.16.3 / 1.33

The version of Helm and Kubernetes where the problem occurs.

Which chart?

The chart name and version.

nr-ebpf-agent

Described what happened, as detailed as possible and necessary.

What you expected to happen?

pods crashloop due to error "too many colons in address"

How to reproduce it?

deploy a cluster with ipv6 only

deploy nri-bundle with newrelic-eapm-agent enabled, or the nr-ebpf-agent chart

Anything else we need to know?

ipv6 address needs to be wrapped in brackets. i did test overriding the otel collector configMap directly with '[$RECEIVER_ENDPOINT]' and the otel pods come up after restarting the pods.

please add the ability to override the RECEIVER_ENDPOINT, in the same way you can override receiverPort: in values https://github.com/newrelic/helm-charts/blob/master/charts/nr-ebpf-agent/values.yaml#L170C1-L171C1

other thoughts:

extraEnv: is commonly found in other newrelic charts. is there a reason it is not included in this chart?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugCategorizes issue or PR as related to a bug.triage/pendingIssue or PR is pending for triage and prioritization.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions