You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
We already added --zap-log-level debug as seen in the attached log. If any additional parameters can help we will add them.
The operator gives itself the required permissions, so it's probably not the problem. We use the default resources.
The only possible reason for the error I can think of is that the cluster has no direct Internet access, but it can pull Docker images from the configured Docker proxy.
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.
The text was updated successfully, but these errors were encountered: