search

jaegertracing / helm-charts

Helm Charts for Jaeger backend
Apache License 2.0
265 stars 340 forks source link

CRDs out of sync with master - causes error: "failed to store the running status into the current CustomResource" #217

Open ggolub opened 3 years ago

ggolub commented 3 years ago

I'm using the jaeger-operator and cluster roles and was able to deploy successfully. I then configured with this code:

apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
  name: simplest

After configuring I get errors like this in the operator log:

time="2021-03-12T15:37:18Z" level=error msg="failed to store the running status into the current CustomResource" error="jaegers.jaegertracing.io \"simplest\" not found" execution="2021-03-12 15:37:09.290528595 +0000 UTC" instance=simplest namespace=observability

I think I've tracked this down to an issue with the CRDs shipped with the helm chart.

If I first manually install the CRDs from https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/crds/jaegertracing.io_jaegers_crd.yaml, using kubectl, everything seems OK. If I don't, I still see the CRDs that get deployed from the operator helm chart but they don't work. I compared them and there are significant differences.

I posted this to the jaegertracing group (https://groups.google.com/g/jaeger-tracing/c/iwtDzCwq6qA) and it was suggested that I open an issue as the CRDs may be out of sync.

jpkrohling commented 3 years ago

For the record: when there are conflicts, the CRD from the jaeger-operator takes precedence.