CRDs

[Gary Golub]

Very new to Jaeger so please bear with me.

I'm trying to wrap the deployment in Terraform using the helm charts (jaegertracing/jaeger-operator v2.19.1).  I'm using the jaeger-operator and cluster roles and was able to deploy that successfully.  However, after configuring using the simplest example 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.

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 dont', 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.

Questions (first specific to this issue, the rest general):

1. Should the operator helm chart CRDs match jaegertracing.io_jaegers_crd.yaml or is pre-installing the latter necessary?  If so, is there a helm chart for those that I haven't found?
2. If I install jaegertracing/jaeger-operator, do I also need to install  jaegertracing/jaeger or is that an alternate deployment w/o the operator?
3. If I configure to use the agent DaemonSet, should I see agent pods in each namespace?  I did, when installing jaegertracing/jaeger (before moving to the operator) and wasn't clear if the operator would create those pods.

Any help is greatly appreciated as I ramp up on this.

[Juraci Paixão Kröhling]

On 12.03.21 16:58, Gary Golub wrote:

> Questions (first specific to this issue, the rest general):
>

> 1. Should the operator helm chart CRDs match

> jaegertracing.io_jaegers_crd.yaml or is pre-installing the latter
> necessary?  If so, is there a helm chart for those that I haven't found?

They are probably out of sync, the one from the jaeger-operator
repository takes precedence. Could you open an issue against the
helm-chart repository?

> 2. If I install jaegertracing/jaeger-operator, do I also need to

> install  jaegertracing/jaeger or is that an alternate deployment w/o
> the operator?

That's an alternate deployment.

> 3. If I configure to use the agent DaemonSet, should I see agent pods

> in each namespace?  I did, when installing jaegertracing/jaeger
> (before moving to the operator) and wasn't clear if the operator
> would create those pods.

No, there should be one DaemonSet for every kubelet node, not namespace.
If you have only one node in your cluster, you'll have only one pod with
the agent.

- Juca.