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
I have noticed after doing a few upgrades that I need to cycle pods to get the updated sidecar and auto-instrumentation as it seems to break and throw errors on the webhook in the manager. Is there a recommended process to prevent this?
Steps to Reproduce
Install version 0.115.0 of the operator.
Deploy a pod with autoinstrumentation and a sidecar collector
Upgrade to version 0.116.x
Expected Result
The autoinstrumentation upgrades and so does the sidecar collector without requiring the pods to be deleted. Or at least not throw errors.
Actual Result
Errors occur and the auto instrumentation and sidecar collector do not get redeployed.
{"level":"ERROR","timestamp":"2025-01-09T15:52:45.043638118Z","logger":"instrumentation-upgrade","message":"failed to apply changes to instance","name":"java-sidecar-instrumentation","namespace":"opentelemetry-operator-system","error":"Internal error occurred: failed calling webhook \"minstrumentation.kb.io\": failed to call webhook: Post \"https://opentelemetry-operator-webhook-service.opentelemetry-operator-system.svc:443/mutate-opentelemetry-io-v1alpha1-instrumentation?timeout=10s\": no endpoints available for service \"opentelemetry-operator-webhook-service\"","stacktrace":"github.com/open-telemetry/opentelemetry-operator/pkg/instrumentation/upgrade.(*InstrumentationUpgrade).ManagedInstances\n\t/home/runner/work/opentelemetry-operator/opentelemetry-operator/pkg/instrumentation/upgrade/upgrade.go:93\nmain.addDependencies.func2\n\t/home/runner/work/opentelemetry-operator/opentelemetry-operator/main.go:548\nsigs.k8s.io/controller-runtime/pkg/manager.RunnableFunc.Start\n\t/home/runner/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/manager/manager.go:307\nsigs.k8s.io/controller-runtime/pkg/manager.(*runnableGroup).reconcile.func1\n\t/home/runner/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/manager/runnable_group.go:226"}
{"level":"ERROR","timestamp":"2025-01-09T15:52:45.046831977Z","logger":"collector-upgrade","message":"failed to apply changes to instance","name":"pod-sidecar","namespace":"opentelemetry-operator-system","error":"Internal error occurred: failed calling webhook \"mopentelemetrycollectorbeta.kb.io\": failed to call webhook: Post \"https://opentelemetry-operator-webhook-service.opentelemetry-operator-system.svc:443/mutate-opentelemetry-io-v1beta1-opentelemetrycollector?timeout=10s\": no endpoints available for service \"opentelemetry-operator-webhook-service\"","stacktrace":"github.com/open-telemetry/opentelemetry-operator/pkg/collector/upgrade.VersionUpgrade.ManagedInstances\n\t/home/runner/work/opentelemetry-operator/opentelemetry-operator/pkg/collector/upgrade/upgrade.go:86\nmain.addDependencies.func1\n\t/home/runner/work/opentelemetry-operator/opentelemetry-operator/main.go:534\nsigs.k8s.io/controller-runtime/pkg/manager.RunnableFunc.Start\n\t/home/runner/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/manager/manager.go:307\nsigs.k8s.io/controller-runtime/pkg/manager.(*runnableGroup).reconcile.func1\n\t/home/runner/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/manager/runnable_group.go:226"}
{"level":"ERROR","timestamp":"2025-01-09T15:52:45.049590845Z","logger":"instrumentation-upgrade","message":"failed to apply changes to instance","name":"nodejs-sidecar-instrumentation","namespace":"opentelemetry-operator-system","error":"Internal error occurred: failed calling webhook \"minstrumentation.kb.io\": failed to call webhook: Post \"https://opentelemetry-operator-webhook-service.opentelemetry-operator-system.svc:443/mutate-opentelemetry-io-v1alpha1-instrumentation?timeout=10s\": no endpoints available for service \"opentelemetry-operator-webhook-service\"","stacktrace":"github.com/open-telemetry/opentelemetry-operator/pkg/instrumentation/upgrade.(*InstrumentationUpgrade).ManagedInstances\n\t/home/runner/work/opentelemetry-operator/opentelemetry-operator/pkg/instrumentation/upgrade/upgrade.go:93\nmain.addDependencies.func2\n\t/home/runner/work/opentelemetry-operator/opentelemetry-operator/main.go:548\nsigs.k8s.io/controller-runtime/pkg/manager.RunnableFunc.Start\n\t/home/runner/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/manager/manager.go:307\nsigs.k8s.io/controller-runtime/pkg/manager.(*runnableGroup).reconcile.func1\n\t/home/runner/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/manager/runnable_group.go:226"}
{"level":"ERROR","timestamp":"2025-01-09T15:52:45.055291592Z","logger":"instrumentation-upgrade","message":"failed to apply changes to instance","name":"dotnet-sidecar-instrumentation","namespace":"opentelemetry-operator-system","error":"Internal error occurred: failed calling webhook \"minstrumentation.kb.io\": failed to call webhook: Post \"https://opentelemetry-operator-webhook-service.opentelemetry-operator-system.svc:443/mutate-opentelemetry-io-v1alpha1-instrumentation?timeout=10s\": no endpoints available for service \"opentelemetry-operator-webhook-service\"","stacktrace":"github.com/open-telemetry/opentelemetry-operator/pkg/instrumentation/upgrade.(*InstrumentationUpgrade).ManagedInstances\n\t/home/runner/work/opentelemetry-operator/opentelemetry-operator/pkg/instrumentation/upgrade/upgrade.go:93\nmain.addDependencies.func2\n\t/home/runner/work/opentelemetry-operator/opentelemetry-operator/main.go:548\nsigs.k8s.io/controller-runtime/pkg/manager.RunnableFunc.Start\n\t/home/runner/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/manager/manager.go:307\nsigs.k8s.io/controller-runtime/pkg/manager.(*runnableGroup).reconcile.func1\n\t/home/runner/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/manager/runnable_group.go:226"}
Additional context
No response
The text was updated successfully, but these errors were encountered:
Component(s)
collector, auto-instrumentation
What happened?
Description
I have noticed after doing a few upgrades that I need to cycle pods to get the updated sidecar and auto-instrumentation as it seems to break and throw errors on the webhook in the manager. Is there a recommended process to prevent this?
Steps to Reproduce
Expected Result
The autoinstrumentation upgrades and so does the sidecar collector without requiring the pods to be deleted. Or at least not throw errors.
Actual Result
Errors occur and the auto instrumentation and sidecar collector do not get redeployed.
Kubernetes Version
1.29
Operator version
0.116.0
Collector version
0.116.1
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: