[Feature Request] Ability to set `automq.zone.cidr.blocks` via static config

[z0rc]

Who is this feature for?

Kafka operator

What problem are they facing today?

It appears that automq.zone.cidr.blocks config option isn't settable via static server.properties. It can be set only via kafka-config.

Why is solving this impactful?

Strimzi Operator sets all user provided options via static config. It assembles config map and mounts it as /opt/kafka/custom-config/service.properties to Kafka broker pod.

Following example at https://github.com/AutoMQ/automq-labs/blob/7b6cad4db34d61250c4d31de26606fe636671fa8/opensource-examples/setup/kubernetes/strimzi/automq-demo.yaml#L153 and guide at https://www.automq.com/docs/automq/eliminate-inter-zone-traffics/broker-configuration user sets automq.zone.cidr.blocks in spec.kafka.config and expects this setting to be successfully applied. Which isn't the case now.

Proposed solution

Make automq.zone.cidr.blocks settable by Strimzi Operator static config.

Additional notes

Slack thread https://automq.slack.com/archives/C06AHBV5NG7/p1766141279031499

[z0rc]

In addition, can automq.zone.cidr.blocks be set as non-sensitive?

Right now it's hard to validate, what is the current value of this config.

[kafka@observability-broker-0 kafka]$ ./bin/kafka-configs.sh --broker-defaults --describe --bootstrap-server localhost:9092
Default configs for brokers in the cluster are:
  automq.zone.cidr.blocks=null sensitive=true synonyms={DYNAMIC_DEFAULT_BROKER_CONFIG:automq.zone.cidr.blocks=null}