Open sergeykad opened 1 day ago
does the manager pod have any reason for its crash? OOMKilled maybe? I haven't been able to reproduce this.
There was no reason at all. It just died and a new pod started. It looks like something crashed during instrumentation injection since it's the last message and it never added the sidecar.
I performed a similar deployment on a Minikube and it works fine but crashes on our production Kubernetes. If there is an option to enable more detailed logs or do some other test I can try it.
you can follow the guide here on how to enable debug logs https://github.com/open-telemetry/opentelemetry-operator/blob/main/DEBUG.md, is it possible the operator doesn't have the permission to do mutation?
Component(s)
auto-instrumentation
What happened?
Description
opentelemetry-operator manager crashes
Steps to Reproduce
Expected Result
A side-car is added to the pod and the service is instrumented with open-telemetry.
Actual Result
opentelemetry-operator crashes with the log seen below.
Kubernetes Version
1.25
Operator version
v0.109.0
Collector version
v0.69.0
Environment information
Environment
OS: Rocky Linux 9.3
Log output
Additional context
There are no additional log messages. The manager just disappears.