Are there default quota settings in a Strimzi Kafka cluster?

[jslusher]

Strimzi version: 0.36.0
Kafka version: 3.4.0

I'm noticing there are a ton of these logs generated in our Kafka cluster:

INFO Removing CONTROLLER_MUTATION quota for user my-one-user (kafka.server.ControllerMutationQuotaManager) [/config/changes-event-process-thread]"
INFO Sensor for user my-one-user already exists. Changing quota to 9.223372036854776E18 in MetricConfig (kafka.server.ClientRequestQuotaManager) [/config/changes-event-process-thread]"
INFO Removing REQUEST quota for user my-one-user (kafka.server.ClientRequestQuotaManager) [/config/changes-event-process-thread]"
INFO Sensor for user my-one-user already exists. Changing quota to 9.223372036854776E18 in MetricConfig (kafka.server.ClientQuotaManager) [/config/changes-event-process-thread]"
INFO Removing FETCH quota for user my-one-user (kafka.server.ClientQuotaManager) [/config/changes-event-process-thread]"
INFO Sensor for user my-one-user already exists. Changing quota to 9.223372036854776E18 in MetricConfig (kafka.server.ClientQuotaManager) [/config/changes-event-process-thread]"
INFO Removing PRODUCE quota for user my-one-user (kafka.server.ClientQuotaManager) [/config/changes-event-process-thread]"
INFO Removing CONTROLLER_MUTATION quota for user my-other-user (kafka.server.ControllerMutationQuotaManager) [/config/changes-event-process-thread]"
....

Are there default quotas set for users? The documentation that I can find about it seems like there shouldn't be, but I can't tell for certain. We're using the KafkaUser Strimzi rsource for what it's worth.

[scholzj]

Support for default Kafka quotas is in progress in #9895. Up to Strimzi 0.38, Strimzi would have deleted the default quotas if you set them. From 0.38 on (#9099), it would ignore them if you set them manually through some API.

[jslusher]

What's suspicious to me is the logs that say Removing X quota for user .... I hadn't inspected the User operator to see if there was anything in there that might give an indication. I see a lot of log entries like this in the user operator:

2024-06-18 17:45:59 WARN  StatusUtils:151 - Reconciliation #379718(timer) KafkaUser(strimzi-kafka-cluster/REDACTED): Contains object at path spec.authorization.acls.resource with unknown properties: name, patternType

I tried using watch to run several bin/kafka-configs.sh --describe --entity-type users commands in a row but I haven't seen any changes to the output so far.

I do see a correlation between reconciliations in the User operator and the logs mentioning quotas in the Kafka cluster, so I do think the User operator is causing all the logging about quota, I just haven't been able to tell if it's actually removing a quota that got set somewhere else or if the logs are standard for some other reason.

[scholzj]

I see a lot of log entries like this in the user operator:

That suggests you have some KafkaUser resources with some invalid YAML I guess.

[jslusher]

Those logs are most likely because I set name and patternType in my type: cluster ACL resources:

      resource:
        name: kafka-cluster
        patternType: literal
        type: cluster

I'm going to clean those up for what it's worth. I'm skeptical that it will help with the quota logging, but we'll see.

[jslusher]

Confirmed that removing patternType and name from user ACLs got rid of those WARN messages. Still plenty of the quota messages though :\

[scholzj]

Well, that warning message definitely didn't had any relation to setting quotas, so no, that would not change anything.