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'm deploying the otel collector via a helm chart to my k8s cluster. I'm trying to update beyond v 0.103.0, but I can't get my health_check extension to survive the 0.0.0.0 -> localhost change in v 0.104.0. I can't set the UseLocalHostAsDefaultHost featuregate, since I'm deploying otel as part of a bigger chart and have no control over the CLI. I'm trying to set the health_check's endpoint to 0.0.0.0:13133 explicitly, but no matter what syntax I try, deployment fails with
cannot unmarshal string into Go struct field OpenTelemetryCollectorSpec.spec.config of type v1beta1.Config
Sorry, no idea, but this sounds like an issue for the operator project. Try with the latest release and proceed from there to create a small reproduction case to send to the operator issues.
Component(s)
No response
Describe the issue you're reporting
Description
I'm deploying the otel collector via a helm chart to my k8s cluster. I'm trying to update beyond v 0.103.0, but I can't get my health_check extension to survive the 0.0.0.0 -> localhost change in v 0.104.0. I can't set the UseLocalHostAsDefaultHost featuregate, since I'm deploying otel as part of a bigger chart and have no control over the CLI. I'm trying to set the health_check's endpoint to 0.0.0.0:13133 explicitly, but no matter what syntax I try, deployment fails with
cannot unmarshal string into Go struct field OpenTelemetryCollectorSpec.spec.config of type v1beta1.Config
chart:
Removing the single endpoint line from health_check causes config to pass fine. I've tried with & without various quotes, http:// prefix, checked whitespaces & indentation are correct, and using a health_check/1: entry as described here: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/extension/healthcheckextension/README.md . What am I missing?
The text was updated successfully, but these errors were encountered: