diff --git a/README.md b/README.md
index 5b348a64..e0fe7759 100644
--- a/README.md
+++ b/README.md
@@ -22,7 +22,7 @@ You can then run `helm search repo trino` to see the charts.
 Then you can install chart using:
 
 ```console
-helm install my-trino trino/trino --version 0.6.0
+helm install my-trino trino/trino --version 0.7.0
 ```
 
 ## Documentation
diff --git a/charts/trino/Chart.yaml b/charts/trino/Chart.yaml
index b856398c..1fc69886 100644
--- a/charts/trino/Chart.yaml
+++ b/charts/trino/Chart.yaml
@@ -15,7 +15,7 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.6.0
+version: 0.7.0
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
diff --git a/charts/trino/README.md b/charts/trino/README.md
index 17e5ebad..10b17df9 100644
--- a/charts/trino/README.md
+++ b/charts/trino/README.md
@@ -56,6 +56,16 @@ The following table lists the configurable parameters of the Trino chart and the
 | `serviceAccount.name` |  | `""` |
 | `serviceAccount.annotations` |  | `{}` |
 | `secretMounts` |  | `[]` |
+| `coordinator.jvm.maxHeapSize` |  | `"8G"` |
+| `coordinator.jvm.gcMethod.type` |  | `"UseG1GC"` |
+| `coordinator.jvm.gcMethod.g1.heapRegionSize` |  | `"32M"` |
+| `coordinator.additionalJVMConfig` |  | `{}` |
+| `coordinator.resources` |  | `{}` |
+| `worker.jvm.maxHeapSize` |  | `"8G"` |
+| `worker.jvm.gcMethod.type` |  | `"UseG1GC"` |
+| `worker.jvm.gcMethod.g1.heapRegionSize` |  | `"32M"` |
+| `worker.additionalJVMConfig` |  | `{}` |
+| `worker.resources` |  | `{}` |
 
 
 
diff --git a/charts/trino/values-coordinator.yaml b/charts/trino/values-coordinator.yaml
deleted file mode 100644
index a221fac9..00000000
--- a/charts/trino/values-coordinator.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Default values for trino coordinator.
-# This is a YAML-formatted file.
-# Declare variables to be passed into your templates.
-
-coordinator:
-  jvm:
-    maxHeapSize: "8G"
-    gcMethod:
-      type: "UseG1GC"
-      g1:
-        heapRegionSize: "32M"
-
-  additionalJVMConfig: {}
-
-  resources: {}
-    # We usually recommend not to specify default resources and to leave this as a conscious
-    # choice for the user. This also increases chances charts run on environments with little
-    # resources, such as Minikube. If you do want to specify resources, uncomment the following
-    # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
-    # limits:
-    #   cpu: 100m
-    #   memory: 128Mi
-    # requests:
-    #   cpu: 100m
-    #   memory: 128Mi 
\ No newline at end of file
diff --git a/charts/trino/values-worker.yaml b/charts/trino/values-worker.yaml
deleted file mode 100644
index 4eaf0f5a..00000000
--- a/charts/trino/values-worker.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Default values for trino worker.
-# This is a YAML-formatted file.
-# Declare variables to be passed into your templates.
-
-worker:
-  jvm:
-    maxHeapSize: "8G"
-    gcMethod:
-      type: "UseG1GC"
-      g1:
-        heapRegionSize: "32M"
-
-  additionalJVMConfig: {}
-
-  resources: {}
-    # We usually recommend not to specify default resources and to leave this as a conscious
-    # choice for the user. This also increases chances charts run on environments with little
-    # resources, such as Minikube. If you do want to specify resources, uncomment the following
-    # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
-    # limits:
-    #   cpu: 100m
-    #   memory: 128Mi
-    # requests:
-    #   cpu: 100m
-    #   memory: 128Mi 
\ No newline at end of file
diff --git a/charts/trino/values.yaml b/charts/trino/values.yaml
index 202ed352..b421a860 100644
--- a/charts/trino/values.yaml
+++ b/charts/trino/values.yaml
@@ -102,3 +102,47 @@ serviceAccount:
   annotations: {}
 
 secretMounts: []
+
+coordinator:
+  jvm:
+    maxHeapSize: "8G"
+    gcMethod:
+      type: "UseG1GC"
+      g1:
+        heapRegionSize: "32M"
+
+  additionalJVMConfig: {}
+
+  resources: {}
+    # We usually recommend not to specify default resources and to leave this as a conscious
+    # choice for the user. This also increases chances charts run on environments with little
+    # resources, such as Minikube. If you do want to specify resources, uncomment the following
+    # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
+    # limits:
+    #   cpu: 100m
+    #   memory: 128Mi
+    # requests:
+    #   cpu: 100m
+    #   memory: 128Mi
+
+worker:
+  jvm:
+    maxHeapSize: "8G"
+    gcMethod:
+      type: "UseG1GC"
+      g1:
+        heapRegionSize: "32M"
+
+  additionalJVMConfig: {}
+
+  resources: {}
+    # We usually recommend not to specify default resources and to leave this as a conscious
+    # choice for the user. This also increases chances charts run on environments with little
+    # resources, such as Minikube. If you do want to specify resources, uncomment the following
+    # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
+    # limits:
+    #   cpu: 100m
+    #   memory: 128Mi
+    # requests:
+    #   cpu: 100m
+    #   memory: 128Mi