externalize Kafka access

Signed-off-by: Jürgen Hemelt <juergen.hemelt@atruvia.de>
Signed-off-by: Tunç Taylan Turunç <tunc_taylan.turunc@atruvia.de>

charts/egeria-base/templates/kafka-cluster.yaml

@@ -14,16 +14,18 @@ spec:
         port: 9092
         type: internal
         tls: false
+{{ if .Values.strimzi.externalListener.enabled }}
       - name: external
         port: 9094
         type: nodeport
         tls: false
         configuration:
           bootstrap:
-            nodePort: {{ .Values.strimzi.bootstrapNodePort }}
+            nodePort: {{ .Values.strimzi.externalListener.bootstrapNodePort }}
           brokers:
           - broker: 0
-            advertisedHost: {{ .Values.strimzi.advertisedHost }}
+            advertisedHost: {{ .Values.strimzi.externalListener.advertisedHost }}
+{{ end }}
     config:
       offsets.topic.replication.factor: 1
       transaction.state.log.replication.factor: 1

charts/egeria-base/values.yaml

@@ -113,11 +113,14 @@ image:
 # will create cluster-scoped resources. Set to false to skip this when in a restricted environment, or needing multiple
 # installs of egeria charts in the same cluster. Requires the strimzi operator to be
 # installed on the cluster by an admin, or a prior install
-# If strimzi is installed, a Kafka cluster is also configured. You can change NodePort options of the external listener.
+# If strimzi is installed, a Kafka cluster is also configured. 
+# You are able to externalize the Kafka access by changing the externalListener options.
 strimzi:
   enabled: true
-  advertisedHost: localhost
-  bootstrapNodePort: 32000
+  externalListener:
+    enabled: true
+    advertisedHost: localhost
+    bootstrapNodePort: 32000
 
 # If you allow (as is default) this chart to install the strimzi operator, this setting will
 # then allow it to work across all namespaces - so for example it will work if installing another