How to set es-provision using jaeger operator

[ErikXu]

I am using the jaeger operator v1.22.1 to create a jaeger instance with self provisioned elasticsearch. I get this message
level=warning msg="An Elasticsearch cluster should be provisioned, but provisioning is disabled for this Jaeger Operator" instance=jaeger namespace=istio-system from the jaeger pod.

I might need to set the flag --es-provision=true, but I can not find a place to do so.

Here is my crd yaml:

apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
  namespace: istio-system
  name: jaeger
spec:
  strategy: production
  storage:
    type: elasticsearch
    elasticsearch:
      nodeCount: 1
      storage:
        storageClassName: gp2
        size: 5Gi
      resources:
        requests:
          cpu: 200m
          memory: 2Gi
        limits:
          cpu: 1000m
          memory: 4Gi
      redundancyPolicy: ZeroRedundancy
  collector:
    options:
      collector.zipkin.host-port: ':9411'
    replicas: 1
    resources:
      requests:
        cpu: 100m
        memory: 128Mi
      limits:
        cpu: 100m
        memory: 128Mi
  query:
    replicas: 1
    labels:
      sidecar.jaegertracing.io/injected: "false"
    resources:
      requests:
        cpu: 100m
        memory: 128Mi
      limits:
        cpu: 100m
        memory: 128Mi

[jpkrohling]

The flag --es-provision=true is an operator one and should be set in the Kubernetes deployment for the operator, similar to this example:

https://github.com/jaegertracing/jaeger-operator/blob/e9d1a5ea0820685f81b93b52d46ef5616e924e6e/examples/operator-with-tracing.yaml#L26

[jpkrohling]

In time, if there's an ES operator in the cluster and the operator is stating that auto-provisioning is disabled, then it thinks you have an explicit flag disabling it. If that's not the case, it's likely a bug and we would appreciate a report about it.

[ErikXu]

Thanks for replying.
There's no ES operator in my cluster. I think the --es-provision flag is auto by default.
And maybe the below code leds to the issue:
https://github.com/jaegertracing/jaeger-operator/blob/v1.22.1/pkg/controller/jaeger/jaeger_controller.go#L275

Operator should also apply ES when es-provision equals auto?

[ErikXu]

BTW, the self provisioned ES seems to work in openshift only ?
After setting --es-provision=true or --es-provision=yes similar to your example, I met anthor problem:

level=error msg="failed to apply the changes" error="no matches for kind \"Elasticsearch\" in version \"logging.openshift.io/v1\"" execution="2021-12-28 11:22:35.395257081 +0000 UTC" instance=jaeger namespace=istio-system

Is it because the cluset is on-promise or there's no ES operator in the cluser ?

[jpkrohling]

If you don't have the ES operator, the auto-provisioning of ES clusters can't be done.

[ErikXu]

Thanks, I will try again with ES operator installed.