Hard-Coded to First Container in Pod - Fails to Inject Agent with Istio

[PlexusLoganPope]

Description

The container injector is hard-coded to inject the New Relic agent into the first container in the pod. In my case, this causes the agent to be injected into the Istio sidecar container instead of the application container, leading to non-functionality.

• https://github.com/newrelic/k8s-agents-operator/blob/main/src/apm/java.go#L64

Steps to Reproduce

1. Set up a Kubernetes pod with Istio sidecar injection enabled.
2. Deploy an application where the application container is not the first container in the pod.
3. Configure New Relic K8s Agent Operator to inject the agent.
4. Observe that the agent is injected into the first container (Istio sidecar), not the application container.

Expected Behavior

The New Relic agent should be injected into a specified application container, not the Istio sidecar.

Actual Behavior

The New Relic agent is injected into the first container in the pod, which in this case is the Istio sidecar container.

Suggested Solution:

Allow the container injector to target a specific container within the pod, provide a mechanism to configure which container the agent should be injected into.

Your Environment

K8s with Istio

[anthonynguyen394]

This issue is happening with Dapr as well, as Dapr runs as the sidecar container alongside the application container.