Strimzi cluster operator crashes when deploying a Kafka cluster manifest in Minikube

[orCellebrite]

Environment

Minikube (8GB RAM devoted to it)
Linux machine on AWS
Instance type t2.2xlarge

Deployed strimzi-cluster-operator using Helm chart:

helm repo add strimzi https://strimzi.io/charts
helm install strimzi-kafka-operator -n kafka strimzi/strimzi-kafka-operator --version 0.29.0

Deploying this Kafka configuration:

apiVersion: kafka.strimzi.io/v1beta2
kind: Kafka
metadata:
  name: my-cluster
  namespace: kafka
spec:
  kafka:
    version: 3.2.0
    replicas: 1
    listeners:
      - name: plain
        port: 9092
        type: internal
        tls: false
      - name: tls
        port: 9093
        type: internal
        tls: true
      - name: external
        port: 9094
        type: loadbalancer
        tls: false
    config:
      offsets.topic.replication.factor: 1
      transaction.state.log.replication.factor: 1
      transaction.state.log.min.isr: 1
      default.replication.factor: 1
      min.insync.replicas: 1
      inter.broker.protocol.version: "3.2"
    storage:
      type: ephemeral
  zookeeper:
    replicas: 3
    storage:
      type: ephemeral
  entityOperator:
    topicOperator: {}
    userOperator: {}

Operator logs:

2022-06-02 16:38:24 INFO  ClusterOperator:79 - Creating ClusterOperator for namespace kafka
2022-06-02 16:38:24 INFO  ClusterOperator:94 - Starting ClusterOperator for namespace kafka
2022-06-02 16:38:24 INFO  ClusterOperator:113 - Opened watch for Kafka operator
2022-06-02 16:38:24 INFO  ClusterOperator:113 - Opened watch for KafkaMirrorMaker operator
2022-06-02 16:38:24 INFO  ClusterOperator:113 - Opened watch for KafkaConnect operator
2022-06-02 16:38:24 INFO  ClusterOperator:113 - Opened watch for KafkaBridge operator
2022-06-02 16:38:24 INFO  ClusterOperator:113 - Opened watch for KafkaMirrorMaker2 operator
2022-06-02 16:38:24 INFO  ClusterOperator:125 - Setting up periodic reconciliation for namespace kafka
2022-06-02 16:38:24 INFO  ClusterOperator:192 - ClusterOperator is now ready (health server listening on 8080)
2022-06-02 16:38:24 INFO  Main:155 - Cluster Operator verticle started in namespace kafka without label selector
2022-06-02 16:40:24 INFO  ClusterOperator:128 - Triggering periodic reconciliation for namespace kafka
2022-06-02 16:40:24 WARN  VersionUsageUtils:60 - The client is using resource type 'kafkas' with unstable version 'v1beta2'
2022-06-02 16:40:24 WARN  VersionUsageUtils:60 - The client is using resource type 'kafkamirrormakers' with unstable version 'v1beta2'
2022-06-02 16:40:24 WARN  VersionUsageUtils:60 - The client is using resource type 'kafkaconnects' with unstable version 'v1beta2'
2022-06-02 16:40:24 WARN  VersionUsageUtils:60 - The client is using resource type 'kafkamirrormaker2s' with unstable version 'v1beta2'
2022-06-02 16:40:24 WARN  VersionUsageUtils:60 - The client is using resource type 'kafkabridges' with unstable version 'v1beta2'
2022-06-02 16:40:24 WARN  VersionUsageUtils:60 - The client is using resource type 'kafkarebalances' with unstable version 'v1beta2'
2022-06-02 16:40:24 WARN  VersionUsageUtils:60 - The client is using resource type 'kafkaconnectors' with unstable version 'v1beta2'
2022-06-02 16:42:24 INFO  ClusterOperator:128 - Triggering periodic reconciliation for namespace kafka
2022-06-02 16:44:24 INFO  ClusterOperator:128 - Triggering periodic reconciliation for namespace kafka
2022-06-02 16:44:52 INFO  OperatorWatcher:38 - Reconciliation #1(watch) Kafka(kafka/my-cluster): Kafka my-cluster in namespace kafka was ADDED
2022-06-02 16:44:52 INFO  AbstractOperator:226 - Reconciliation #1(watch) Kafka(kafka/my-cluster): Kafka my-cluster will be checked for creation or modification
2022-06-02 16:44:52 INFO  OperatorWatcher:38 - Reconciliation #2(watch) Kafka(kafka/my-cluster): Kafka my-cluster in namespace kafka was MODIFIED
2022-06-02 16:44:52 INFO  CrdOperator:113 - Reconciliation #1(watch) Kafka(kafka/my-cluster): Status of Kafka my-cluster in namespace kafka has been updated
2022-06-02 16:44:57 WARN  VersionUsageUtils:60 - The client is using resource type 'strimzipodsets' with unstable version 'v1beta2'

Pod action after applying this manifest:

kubectl get pods -n kafka -w
kubectl apply -f kafka.yaml

k get pods -n kafka -w
NAME                                        READY   STATUS              RESTARTS        AGE
strimzi-cluster-operator-7c77f74847-r9hs9   1/1     Running             6 (3m23s ago)   14m
my-cluster-zookeeper-0                      0/1     Pending             0               0s
my-cluster-zookeeper-0                      0/1     Pending             0               0s
my-cluster-zookeeper-1                      0/1     Pending             0               0s
my-cluster-zookeeper-1                      0/1     Pending             0               0s
my-cluster-zookeeper-2                      0/1     Pending             0               0s
my-cluster-zookeeper-2                      0/1     Pending             0               0s
my-cluster-zookeeper-0                      0/1     ContainerCreating   0               0s
my-cluster-zookeeper-1                      0/1     ContainerCreating   0               0s
my-cluster-zookeeper-2                      0/1     ContainerCreating   0               0s
strimzi-cluster-operator-7c77f74847-r9hs9   0/1     Error               6 (9m25s ago)   20m
my-cluster-zookeeper-2                      0/1     Running             0               2s
my-cluster-zookeeper-1                      0/1     Running             0               2s
my-cluster-zookeeper-0                      0/1     Running             0               2s
strimzi-cluster-operator-7c77f74847-r9hs9   0/1     CrashLoopBackOff    6 (12s ago)     20m
my-cluster-zookeeper-1                      1/1     Running             0               20s
my-cluster-zookeeper-2                      1/1     Running             0               20s
my-cluster-zookeeper-0                      1/1     Running             0               20s

[scholzj]

Perhaps not enough resources or some CPU starvation on the burstable nodes? You should check if the operator has resources set. You can also check the events about why is it failing.