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
An attempt to upgrade from 0.96 to 0.102 has failed for us with:
or: "kubernetes/opentelemetry-operator": error when patching "kubernetes/opentelemetry-operator": conversion webhook for opentelemetry.io/v1alpha1, Kind=OpenTelemetryCollector failed: Post "[https://opentelemetry-operator-webhook-service.system.svc:443/convert?timeout=30s](https://opentelemetry-operator-webhook-service.system.svc/convert?timeout=30s)": service "opentelemetry-operator-webhook-service" not found
The issue is in fact that opentelemetry-operator-webhook-service is deployed in the opentelemetry-operator-system namespace rather than system.
My guess is that it's because of incorrect path here which should be /spec/conversion/webhook/clientConfig/service/namespace and indeed this custom patch resolved an issue for us:
Component(s)
No response
What happened?
Description
An attempt to upgrade from
0.96
to0.102
has failed for us with:The issue is in fact that
opentelemetry-operator-webhook-service
is deployed in theopentelemetry-operator-system
namespace rather thansystem
.My guess is that it's because of incorrect path here which should be
/spec/conversion/webhook/clientConfig/service/namespace
and indeed this custom patch resolved an issue for us:Steps to Reproduce
Upgrade otel collector operator from
0.96
to0.102
. Although I don't quite understand yet why others did not complain.Expected Result
Successul upgrade.
Actual Result
Kube apply fails with
conversion webhook for opentelemetry.io/v1alpha1, Kind=OpenTelemetryCollector failed
Kubernetes Version
1.29.4
Operator version
0.102.0
Collector version
0.102.0
The text was updated successfully, but these errors were encountered: