Srimzi Cruise Control pod not coming up due to forbidden quota

[bharat15-ml]

Describe the bug
Strimzi Cruise Control pod not coming up due to forbidden quota.
while describe deployment and replicaset of cruise control - pods "test-cruise-control-5fbf57f9b7-q8jx6" is forbidden: failed quota:mem-cpu-quota: must specify limits.cpu,limits.memory,requests.cpu,requests.memory

To Reproduce

apiVersion: kafka.strimzi.io/v1beta2
kind: Kafka
metadata:
  name: my-cluster
spec:
  kafka:
    version: 3.1.0
    replicas: 3
    listeners:
      - name: plain
        port: 9092
        type: internal
        tls: false
      - name: tls
        port: 9093
        type: internal
        tls: true
    config:
      offsets.topic.replication.factor: 3
      transaction.state.log.replication.factor: 3
      transaction.state.log.min.isr: 2
      default.replication.factor: 3
      min.insync.replicas: 2
      inter.broker.protocol.version: "3.1"
    storage:
      type: ephemeral
  zookeeper:
    replicas: 3
    storage:
      type: ephemeral
  entityOperator:
    topicOperator: {}
    userOperator: {}
  cruiseControl: 
    brokerCapacity: {}
    config:
      sample.store.topic.replication.factor: 3
      broker.sample.store.topic.partition.count: 32
      resources:
        requests:
          cpu: 1
          memory: 1Gi
        limits:
          cpu: 1
          memory: 1Gi
      template:
        pod:
           metadata:
             labels:
               securityContext:
                 runAsUser: 1000001
                 fsGroup: 0
                 terminationGracePeriodSeconds: 120
      metricsConfig:
         type: jmxPrometheusExporter
         valueFrom:
           configMapKeyRef:
             name: cruise-control-metrics
             key: cruise-control-metrics-config.yml

4. See error

Cruise Control pods not coming up. While checking for reason got in events it is due to - "pods "test-cruise-control-5fbf57f9b7-q8jx6" is forbidden: failed quota:mem-cpu-quota"

Expected behavior
cruise control pod should comeup and should be in running state, like belows:-

Environment (please complete the following information):

• Strimzi version: [e.g. main, 0.28.0]
• Installation method: YAML files, Helm chart
• Kubernetes cluster: Kubernetes 1.22
• Infrastructure: onprem k8s Cluster

Additional error info - I am suspecting it is due to crusie control side car container i.e. tls-sidecar. while check cruise control deployment tls-sidecar resources are be default empty {}.

[scholzj]

I'm not sure I understand why would you be missing resources only for the Cruise Control pod and not for all the other pods deployed before since you do not have resources anywhere in your Kafka CR. But in any case if you need them, you should configure them in there. This is nothing that would deserve opening a bug: https://strimzi.io/docs/operators/latest/full/configuring.html#type-CruiseControlSpec-reference

[bharat15-ml]

my bad, I was not sure on how to specifically specify resources to cruise contrl side car container pod i.e tls-sidecar. it's working fine!!

[scholzj]

Yeah, it should be .spec.cruiseControl.tlsSidecar.resources. In newer versions of Strimzi, the Cruise Control TLS sidecar is not used anymore - that is why it is in the link I shared marked as deprecated.