Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
PlexusLoganPope opened this issue Oct 21, 2024 · 0 comments

Comments

@PlexusLoganPope
Copy link

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.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant