Strimzi cluster operator CrashLoopBackOff

[northboys]

Kafka cluster operator error when i trying to apply new cluster,

2022-02-02 06:26:18 INFO  ClusterOperator:79 - Creating ClusterOperator for namespace kafka-system
2022-02-02 06:26:18 INFO  ClusterOperator:94 - Starting ClusterOperator for namespace kafka-system
2022-02-02 06:26:18 WARN  VersionUsageUtils:60 - The client is using resource type 'kafkas' with unstable version 'v1beta2'
2022-02-02 06:26:20 WARN  VersionUsageUtils:60 - The client is using resource type 'strimzipodsets' with unstable version 'v1beta2'
2022-02-02 06:26:21 INFO  StrimziPodSetController:419 - Starting the StrimziPodSet controller
2022-02-02 06:26:21 INFO  StrimziPodSetController:387 - Starting StrimziPodSet controller for namespace kafka-system
2022-02-02 06:26:21 INFO  StrimziPodSetController:389 - Waiting for informers to sync
2022-02-02 06:26:21 INFO  StrimziPodSetController:394 - Informers are in-sync
2022-02-02 06:26:21 INFO  ClusterOperator:108 - Opened watch for Kafka operator
2022-02-02 06:26:21 INFO  ClusterOperator:108 - Opened watch for KafkaMirrorMaker operator
2022-02-02 06:26:21 INFO  OperatorWatcher:38 - Reconciliation #1(watch) Kafka(kafka-system/my-cluster): Kafka my-cluster in namespace kafka-system was ADDED
2022-02-02 06:26:22 INFO  ClusterOperator:108 - Opened watch for KafkaConnect operator
2022-02-02 06:26:22 INFO  ClusterOperator:108 - Opened watch for KafkaBridge operator
2022-02-02 06:26:22 INFO  ClusterOperator:108 - Opened watch for KafkaMirrorMaker2 operator
2022-02-02 06:26:22 INFO  AbstractOperator:226 - Reconciliation #1(watch) Kafka(kafka-system/my-cluster): Kafka my-cluster will be checked for creation or modification
2022-02-02 06:26:22 INFO  ClusterOperator:119 - Setting up periodic reconciliation for namespace kafka-system
2022-02-02 06:26:24 INFO  ClusterOperator:178 - ClusterOperator is now ready (health server listening on 8080)
2022-02-02 06:26:24 INFO  Main:151 - Cluster Operator verticle started in namespace kafka-system without label selector

[scholzj]

The log does not show any error. So you would need to check the Kubernetes events on why the container was restarted I guess. One possible issue can be insufficient resources?

[northboys]

I already figure out this issue, i try to increase memory limit on Strimzi cluster operator and now working properly.
Thanks.

[josh-cain]

Same - bumped the resources and quit seeing the occasional CrashLoopBackOff. Thanks for asking about this!