<p>I'm following the Dapr documentation to have Dapr sending data to an Open Telemetry collector pod in kubernetes.
The first step is to configure Dapr to send distributed tracing data.
<a href="https://docs.dapr.io/operations/monitoring/tracing/setup-tracing/" rel="nofollow noreferrer">Tracing Docs</a></p>
<p>So I'm trying to add the following yaml file to kubernetes:</p>
<pre><code>apiVersion: dapr.io/v1alpha1
kind: Configuration
metadata:
  name: tracing
spec:
  tracing:
    samplingRate: &quot;1&quot;
    otel:
      endpointAddress: &quot;localhost:4317&quot;
      isSecure: false
      protocol: grpc 
</code></pre>
<p>Using the command: <code>kubectl apply -f .\tracing-config.yaml</code></p>
<p>Problem is that I'm getting the following error:</p>
<blockquote>
<p>error: error validating &quot;.\zeta\components\tracing-config.yaml&quot;: error validating data: ValidationError(Configuration.spec.tracing): unknown field &quot;otel&quot; in io.dapr.v1alpha1.Configuration.spec.tracing; if you choose to ignore these errors, turn validation off with --validate=false</p>
</blockquote>
<p>Even if I try to use <code>kubectl apply -f .\tracing-config.yaml --validate=false</code>, what happens is that the field &quot;otel&quot; and it's subfields are ignored when applied.</p>
<p>Since that yaml exists in Dapr's official documentation, I imagine this should be doable. Is there a way to add a field even if it is not recognized? Or some other workaround for this?</p>

Daniel Patrício
<p>As Juliano Costa mentioned, in fact, I had the dapr sidecars updated, but not dapr it self and the version I was using did not support the &quot;otel&quot; field. Updating it to the version 1.10 fixed it.</p>
