kafka cannot start in mimir charts with this error "Invalid value for configuration broker.id"

[rezacloner1372]

This is my part of the value file. i am trying to deploy Mimir on OpenShift. but i get an error on kafka pod:

│ Exception in thread "main" org.apache.kafka.common.config.ConfigException: Invalid value for configuration broker.id: Not a number of type INT at org.apache.kafka.common.conf │
│ ig.ConfigDef.parseType(ConfigDef.java:776) at org.apache.kafka.common.config.ConfigDef.parseValue(ConfigDef.java:531) at org.apache.kafka.common.config.ConfigDef.parse(Config │
│ Def.java:524) at org.apache.kafka.common.config.AbstractConfig.<init>(AbstractConfig.java:114) at org.apache.kafka.server.config.AbstractKafkaConfig.<init>(AbstractKafkaConfi │
│ g.java:78) at kafka.server.KafkaConfig.<init>(KafkaConfig.scala:156) at kafka.server.KafkaConfig.<init>(KafkaConfig.scala:158) at kafka.tools.StorageTool$.$anonfun$execute$1( │
│ StorageTool.scala:79) at scala.Option.flatMap(Option.scala:283) at kafka.tools.StorageTool$.execute(StorageTool.scala:79) at kafka.tools.StorageTool$.main(StorageTool.scala:4 │
│ 6) at kafka.docker.KafkaDockerWrapper$.main(KafkaDockerWrapper.scala:57) at kafka.docker.KafkaDockerWrapper.main(KafkaDockerWrapper.scala) at java.base@21.0.2/java.lang.invok │
│ e.LambdaForm$DMH/sa346b79c.invokeStaticInit(LambdaForm$DMH)

# other config
kafka:
  enabled: true
  replicas: 3

  persistence:
    enabled: true
    size: 10Gi
    storageClass: "ceph-rbd"

  resources:
    limits:
      cpu: 1000m
      memory: 2Gi
    requests:
      cpu: 500m
      memory: 1Gi

  securityContext:
    fsGroup: null
    runAsUser: null
    runAsGroup: null
    runAsNonRoot: true
    seccompProfile:
      type: RuntimeDefault

  # Container security context
  containerSecurityContext:
    allowPrivilegeEscalation: false
    readOnlyRootFilesystem: true
    capabilities:
      drop: [ ALL ]
# other config

[narqo]

The error Invalid value for configuration broker.id: Not a number of type INT suggests that the container didn't receive the broker id from the pod index. That is, Kafka's initialization scripts derives the broker.id from the pod's ordinal index in its StatefulSet. One potential reason for that is OpenShift's security policies.

Note that we're strongly NOT recommending to use the Kafka, that comes with the Mimir Helm chart, outside a simple demo/testing purposes. Refer to Run Grafana Mimir in production using the Helm chart for details on how to configure an external Kafka cluster, that you can manage outside Mimir.