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

Operator startup dependency #3489

Open
pieterv-icloud-com opened this issue Nov 23, 2024 · 1 comment
Open

Operator startup dependency #3489

pieterv-icloud-com opened this issue Nov 23, 2024 · 1 comment
Labels
area:auto-instrumentation Issues for auto-instrumentation

Comments

@pieterv-icloud-com
Copy link

Component(s)

auto-instrumentation

Describe the issue you're reporting

Hi

We use ArgoCD to deploy our applications as well as the OpenTelemetry Operator

It usually happens that the workload which is annotated for auto instrumentation starts up before the operator is fully installed.

This means the applications opentelemetry environment variables are not populated and that the auto instrumentation pod is never attached as a initContainer.

The way to fix this is to manually delete the pod and then allow it to be recreated once the opentelemetry operator is installed.

Has anyone found a way around this?

@pieterv-icloud-com pieterv-icloud-com changed the title Collector startup dependency Operator startup dependency Nov 23, 2024
@jaronoff97
Copy link
Contributor

this is a longstanding issue and one we haven't come to a decision on how to fix unfortunately. #1329, specifically this comment is where we are stuck

@jaronoff97 jaronoff97 added area:auto-instrumentation Issues for auto-instrumentation and removed needs triage labels Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:auto-instrumentation Issues for auto-instrumentation
Projects
None yet
Development

No branches or pull requests

2 participants