fix(strimzi): fix template to prevent config overrides

[kincoy]

from the docs as we known, the nodepool's template config will overrides the kafka cluster's template config, so if use this demo config, can't inject the access key into pod envs, which cause the pods to fail on starup.

[Rancho-7]

Hi @kincoy , thank you for your contribution!
Could you please confirm if you are using the Strimzi version specified in our documentation here:

automq-labs/opensource-examples/setup/kubernetes/strimzi/README.md

Line 28 in 4c68df7

A pre-configured `strimzi-values.yaml` file is provided in this directory as your starting point. We recommend using the fixed version `0.47` of Strimzi to avoid compatibility issues.

I ask because the screenshot you provided appears to show from the latest Strimzi version, which is 0.49:
https://strimzi.io/docs/operators/latest/deploying.html#con-pod-scheduling-str

[kincoy]

In fact, I was already using the 0.47 operator. I only went to the official Strimzi documentation after I noticed the cluster could not start properly, and that is when I discovered the configuration override issue.

[kincoy]

and i think it's the logic code: https://github.com/strimzi/strimzi-kafka-operator/blob/40b9fa269ba87283bb0651711557922b14d715b3/cluster-operator/src/main/java/io/strimzi/operator/cluster/model/KafkaPool.java#L196C1-L218C10

[kincoy]

I’ve checked the code in both 0.47 and 0.49, and in both versions it appears to be a replacement behavior rather than a merge behavior.

[Rancho-7]

@kincoy Sorry for the late reply. You're right—nice catch!
I tested moving the config to the Kafka cluster template, but it still didn't work. As you pointed out, it behaves like a replacement rather than a merge. I think maybe we should move all the environment configs to KafkaNodePool instead. WDYT?