Jaeger-operator: Kafka customization

[daroga0002]

I am using following definition of operator:

image:
  repository: jaegertracing/jaeger-operator
  tag: 1.18.0
  pullPolicy: IfNotPresent
  imagePullSecrets: []

crd:
  install: true

jaeger:
  create: true
  spec:
    strategy: streaming
    ingester:
      maxReplicas: 8
      resources:
        limits:
          cpu: 100m
          memory: 128Mi
    storage:
      type: elasticsearch
# Disable "Deriving dependencies" feature
      dependencies:
        enabled: false 
      options:
        es:
          use-aliases: true
          server-urls: http://jeager-elasticsearch-master:9200

and this is creating me Kafka using Strizmi operator. Question which I have are there any parameters which can be influence current strimzi created object, especially volume size used by Kafka and zookeeper which currently create me PVC 100GB each (so totally Kafka takes 600GB).

I tried to look but didnt find any docs about this

[daroga0002]

found this https://github.com/jaegertracing/jaeger-operator/blob/c95d177a36102f18feef452983e84bc12a680cd7/pkg/kafka/streaming.go#L28 so I am assuming those values are hardcoded and not customizable?

[objectiser]

@daroga0002 Correct, these are no currently customizable.

Best approach for now would be to setup your kafka cluster separately, and reference the broker with the appropriate options.

@jpkrohling Were there specific reasons why we didn't want to make this field configurable?

[jpkrohling]

We have a flag to the operator binary, making these lower, suitable for testing (--kafka-provisioning-minimal). The reason we don't support customization of the Kafka CR is that we don't want to replicate all their options in our CR. Rather, if you a custom Kafka CR is needed, then it has to be provisioned separately.