build fix? enabled kraft, removed zookeeper + appVersion: staging-latest

deploy-values-lite.yaml

@@ -1,22 +1,13 @@
 image:
   pullPolicy: Always
 
-flink:
-  enabled: false
-
 nussknacker:
   streaming:
     deploymentMode: "lite-k8s"
 
-telegraf:
+flink:
   enabled: false
 
-zookeeper:
+telegraf:
   enabled: false
 
-kafka:
-  kraft:
-    enabled: true
-  externalZookeeper:
-    servers: []
-

src/Chart.lock

@@ -5,11 +5,8 @@ dependencies:
 - name: kafka
   repository: https://charts.bitnami.com/bitnami
   version: 22.1.6
-- name: zookeeper
-  repository: https://charts.bitnami.com/bitnami
-  version: 11.0.3
 - name: apicurio-registry
-  repository: https://helm-charts.touk.pl/public/
+  repository: https://helm-charts.touk.pl/public
   version: 0.1.5
 - name: flink
   repository: https://riskfocus.github.io/helm-charts-public/
@@ -22,6 +19,6 @@ dependencies:
   version: 4.12.5
 - name: telegraf
   repository: https://helm.influxdata.com/
-  version: 1.8.53
-digest: sha256:840544ff09e87b5c7f37c83c8b84ee5fa97c7516c2d6dcdef10de7e44f37b230
-generated: "2024-09-13T16:12:08.987227+02:00"
+  version: 1.8.55
+digest: sha256:04a67925ba27e25d6ac99f89628390604acf5951096777d0b5c717cb24a9dd32
+generated: "2025-02-27T17:22:09.569793976+01:00"

src/Chart.yaml

@@ -12,10 +12,10 @@ keywords:
   - stream processing
   - event stream processing
 type: application
-# latest-staging version is used when someone run the snapshot build of this chart manually. scala_2.12 is because it can be used with Flink
+# staging-latest version is used when someone run the snapshot build of this chart manually.
 # During release it is replaced by the released image version. In the main we should always keep this version
 # TODO The best would be to publish X.Y.Z-latest docker image version in core and use it here to make it more explicit
-appVersion: 1.19.0-SNAPSHOT
+appVersion: staging-latest
 dependencies:
   - name: postgresql
     version: ~12.1.15
@@ -25,10 +25,6 @@ dependencies:
     version: ~22.1.6
     repository: "@bitnami"
     condition: kafka.enabled
-  - name: zookeeper
-    version: ~11.0.3
-    repository: "@bitnami"
-    condition: zookeeper.enabled
   - name: apicurio-registry
     repository: "@touk"
     version: ~0.1.5

src/README.md

@@ -80,8 +80,6 @@ flink:
   enable: false
 telegraf:
   enabled: false  
-zookeeper:
-  enabled: false
 ```
 
 In case if you want to  use only request-response processing mode in your scenarios you can also disable streaming part of the application stack:
@@ -95,8 +93,6 @@ telegraf:
   enabled: false  
 kafka:
   enabled: false
-zookeeper:
-  enabled: false
 apicurio-registry:
   enabled: false
 ```

src/values.yaml

@@ -6,9 +6,6 @@ global:
   kafka:
     name: kafka
     port: 9092
-  zookeeper: &zookeeper_ports_config
-    ports:
-      client: 2181
   schemaRegistry:
     name: apicurio-registry
     path: /apis/ccompat/v6/
@@ -178,21 +175,12 @@ postgresql:
   volumePermissions:
     enabled: true
 
-zookeeper:
-  enabled: true
-  service: *zookeeper_ports_config
-
 kafka:
   enabled: true
   persistence:
     enabled: true
   kraft:
-    enabled: false
-  zookeeper:
-    enabled: false
-  externalZookeeper:
-    servers:
-      - "{{ .Release.Name }}-zookeeper:{{ .Values.global.zookeeper.ports.client }}"
+    enabled: true
 
 apicurio-registry:
   enabled: true