diff --git a/src/Chart.lock b/src/Chart.lock
index bbde2622..e7505b89 100644
--- a/src/Chart.lock
+++ b/src/Chart.lock
@@ -4,7 +4,7 @@ dependencies:
   version: 12.1.15
 - name: kafka
   repository: https://charts.bitnami.com/bitnami
-  version: 22.1.3
+  version: 22.1.6
 - name: zookeeper
   repository: https://charts.bitnami.com/bitnami
   version: 11.0.3
@@ -16,12 +16,12 @@ dependencies:
   version: 0.2.0
 - name: grafana
   repository: https://grafana.github.io/helm-charts
-  version: 6.56.6
+  version: 6.59.4
 - name: influxdb
   repository: https://helm.influxdata.com/
-  version: 4.12.1
+  version: 4.12.5
 - name: telegraf
   repository: https://helm.influxdata.com/
-  version: 1.8.28
-digest: sha256:46aba6b24953b73194810cdde14358f7098d52c4d83708561d1038f9a8a5432b
-generated: "2023-05-31T09:36:02.733938544+02:00"
+  version: 1.8.34
+digest: sha256:a4235f4aca5b0785f910bc33cb813604cab949729753b88fb095814524fe269c
+generated: "2023-09-13T10:29:02.122496096+02:00"
diff --git a/src/Chart.yaml b/src/Chart.yaml
index 6419e76d..a482b8dc 100644
--- a/src/Chart.yaml
+++ b/src/Chart.yaml
@@ -1,6 +1,6 @@
 apiVersion: v2
 name: nussknacker
-version: 1.10.1-mpk-9
+version: 1.11.1-SNAPSHOT
 description: Nussknacker - a design, development, and deployment tool for stream processing
 home: https://nussknacker.io/
 icon: https://nussknacker.io/wp-content/uploads/2021/10/Nussknacker-short-black.svg
@@ -11,14 +11,14 @@ keywords:
   - stream processing
   - event stream processing
 type: application
-appVersion: 1.10.0
+appVersion: 1.11.3
 dependencies:
   - name: postgresql
     version: ~12.1.15
     repository: "@bitnami"
     condition: postgresql.enabled
   - name: kafka
-    version: ~22.1.3
+    version: ~22.1.6
     repository: "@bitnami"
     condition: kafka.enabled
   - name: zookeeper
@@ -39,10 +39,10 @@ dependencies:
     repository: "@grafana"
     condition: grafana.enabled
   - name: influxdb
-    version: ~4.12.0
+    version: ~4.12.5
     repository: "@influxdata"
     condition: influxdb.enabled
   - name: telegraf
-    version: ~1.8.26
+    version: ~1.8.34
     repository: "@influxdata"
     condition: telegraf.enabled
diff --git a/src/README.md b/src/README.md
index 5e44e0f1..e145a954 100644
--- a/src/README.md
+++ b/src/README.md
@@ -7,9 +7,7 @@ it is highly configurable.
 
 Quickstart
 ----------
-To go through the whole process of installation, configuration of messages schemas and defining of scenarios,
-see [Quickstart guide](https://nussknacker.io/documentation/quickstart/helm/)
-or `k8s-helm` directory in [nussknacker-quickstart repository](https://github.com/TouK/nussknacker-quickstart)
+Check [Quickstart guide](https://nussknacker.io/documentation/quickstart/lite-streaming/) relevant to your [engine](https://nussknacker.io/documentation/about/engines/) and [processing mode](https://nussknacker.io/documentation/about/ProcessingModes/) to see the whole process of installation, configuration of messages schemas and defining of scenarios. You can also check `k8s-helm` directory in [nussknacker-quickstart repository](https://github.com/TouK/nussknacker-quickstart) for an example of K8s based installation. Finally, the `examples` folder of the [Helm chart repo](https://github.com/TouK/nussknacker-helm.git) contains examples how to apply configurations typical to Nussknacker K8s deployment. 
 
 Requirements
 ------------
@@ -125,6 +123,10 @@ Nussknacker configuration consists of three [configuration areas](https://nusskn
   - `k8sDeploymentConfig` - here you can specify your own k8s runtime deployment yaml config in `streaming-lite` and `request-response` modes
   - `requestResponse` - here you can specify `servicePort` and `ingress` configuration for deployed scenarios on k8s when running in `request-response` mode
 
+Yaml keys expected by Nussknacker to be in the form of nested yaml structures in the Values file are converted to json; check the chart implementation if in doubt.  
+
+Please note that not all configurations are one-to-one mapped to Values key names and that in few cases Values key names are different from configuration keys names.
+
 Finally, if you use external (not generated through this chart) Flink instance, use `flinkConfig` to configure it. Check `values.yaml` for available options. These settings are included in ```engineConfig``` section   of ```application.conf ```.