[nr-ebpf-agent] The latest 0.4.0 chart fixes the issue with image path selection; and the associated PR enables users to set the image path for the init container #1972
Description
Bug description
My org operates behind a firewall which blocks pulling docker images from public sources; so we typically proxy New Relic images into our own internal repo and Kubernetes pulls them from there.
The new functionality in the ebpf agent chart for selecting the image tag introduced after version 0.2.7 breaks the ability to override the docker repository path unless the image tag is specified.
The previous functionality allowed us to simply provide these values (obfuscated):
ebpfAgent:
image:
repository: docker.my-registry.com/my-org/proxy-cache/newrelic/newrelic-ebpf-agent
ebpfClient:
image:
repository: docker.my-registry.com/my-org/proxy-cache/newrelic/newrelic-ebpf-agent
otelCollector:
image:
repository: docker.my-registry.com/my-org/proxy-cache/newrelic/newrelic-ebpf-agentAnd it would use the tag provided in the values. Now, it automatically picks the docker.io path
Version of Helm and Kubernetes
N/A
Which chart?
nr-ebpf-agent version 0.2.8 and higher
What happened?
Upon upgrading the nri-bundle chart to the latest release (from 6.0.10), we see imagePullBackoff for the ebpf agent and otel collector
What you expected to happen?
The images should be pulled from our internal proxy cache registry
How to reproduce it?
Use a registry that supports proxying images from the public internet, specify the values I provided above and the global.licenseKey and global.clusterName values necessary to install the chart.
Anything else we need to know?
I have a commit ready to support both functionalities and also fix an oversight with the init Container for the ebpf agent. Will share it once I open the PR.