[System Tests] Strimzi Kafka resource producing DeprecatedFields warning #3081
Description
Describe the bug
The system tests create Kafka clusters uses Strimzi to create Kafka resource. I notice that these Kafka resources are reporting deprecation warnings in the CR's status section. These should be cleaned up.
status:
clusterId: aNW84W6lRQaQfUeetRlg8A
conditions:
- lastTransitionTime: "2025-12-18T17:32:51.093789127Z"
message: inter.broker.protocol.version is not used in KRaft-based Kafka clusters
and should be removed from the Kafka custom resource.
reason: KafkaInterBrokerProtocolVersionInKRaft
status: "True"
type: Warning
- lastTransitionTime: "2025-12-18T17:32:51.093866313Z"
message: log.message.format.version is not used in KRaft-based Kafka clusters
and should be removed from the Kafka custom resource.
reason: KafkaLogMessageFormatVersionInKRaft
status: "True"
type: Warning
- lastTransitionTime: "2025-12-18T17:33:19.222935046Z"
status: "True"
type: Ready
- lastTransitionTime: "2025-12-18T17:32:47.692619730Z"
message: In resource Kafka(kafka/metrics-st-cluster) in API version kafka.strimzi.io/v1beta2
the replicas property at path spec.kafka.replicas has been deprecated. Use `KafkaNodePool`
resources.
reason: DeprecatedFields
status: "True"
type: Warning
- lastTransitionTime: "2025-12-18T17:32:47.692619730Z"
message: In resource Kafka(kafka/metrics-st-cluster) in API version kafka.strimzi.io/v1beta2
the storage property at path spec.kafka.storage has been deprecated. Use `KafkaNodePool`
resources.
reason: DeprecatedFields
status: "True"
type: WarningI also notice the system tests aren't creating nodepool resources.
To Reproduce
Steps to reproduce the behavior:
- Run any of the System Tests.
- Watch the Kafka Resources
- Look at the status section.
- Behold the
DeprecatedFieldswarnings.
Expected behavior
Kafka CRs should be created without deprecation warnings.
YAML files and logs
Attach or copy paste your kroxylicious configuration YAML (with sensitive details
like broker address redacted).
Attach or copy and paste relevant logs.
Additional context
Add any other context about the problem here.