Loading...

XML

Word

Printable

Blocked:
False
Blocked Reason:
None
Ready:
False
GSS Priority:
Target Release:

2.3.0.GA
Steps to Reproduce:
Hide

1. Create KafkaTopic CR yaml without "config: {}” as below:

apiVersion: kafka.strimzi.io/v1beta2 kind: KafkaTopic ... spec: partitions: 1

2. oc apply -f <KafkaTopic CR yaml>

3. Check created KafkaTopic using "oc KafkaTopic/my-topic-01"
==> "config: {}” is added automatically.

apiVersion: kafka.strimzi.io/v1beta2 kind: KafkaTopic ... spec: config: {} # Added automatically partitions: 1
Show
1. Create KafkaTopic CR yaml without "config: {}” as below: apiVersion: kafka.strimzi.io/v1beta2 kind: KafkaTopic ... spec: partitions: 1 2. oc apply -f <KafkaTopic CR yaml> 3. Check created KafkaTopic using "oc KafkaTopic/my-topic-01" ==> "config: {}” is added automatically. apiVersion: kafka.strimzi.io/v1beta2 kind: KafkaTopic ... spec: config: {} # Added automatically partitions: 1
Intelligence Requested:
Market:

KafkaTopic "config: {}" is automatically added or removed
- This behavior seems since AMQ Streams 2.1.
  - Oddly as described below, if config: {} in KafkaTopic CR yaml is added, it is removed; but if not, it is automatically added.
- In the case of AMQ Streams 2.0, "config: {}" is always removed, never added.

[As far as I confirmed]

AMQ Streams 2.1
- In the case of creating a KafkaTopic with "config: {}", "config: {}" will be automatically removed.
- In the case of creating a KafkaTopic without "config: {}", "config: {}" will be automatically added.
AMQ Streams 2.0
- In the case of creating a KafkaTopic with "config: {}", "config: {}" will be automatically removed.
- In the case of creating a KafkaTopic without "config: {}", It remains so.