Updated the README

README.md

@@ -1,7 +1,7 @@
 # Helm Chart for GraphDB
 
 [![CI](https://github.com/Ontotext-AD/graphdb-helm/actions/workflows/ci.yml/badge.svg)](https://github.com/Ontotext-AD/graphdb-helm/actions/workflows/ci.yml)
-![Version: 11.1.3](https://img.shields.io/badge/Version-11.1.3-informational?style=flat-square)
+![Version: 11.2.0](https://img.shields.io/badge/Version-11.2.0-informational?style=flat-square)
 ![AppVersion: 10.7.3](https://img.shields.io/badge/AppVersion-10.7.3-informational?style=flat-square)
 
 <!--
@@ -310,6 +310,19 @@ IMPORTANT: This is generated by helm-docs, do not attempt modifying it on hand a
 | annotations | object | `{}` |  |
 | args | list | `[]` |  |
 | automountServiceAccountToken | bool | `false` |  |
+| backup.cloud.bucketUri | string | `""` |  |
+| backup.enabled | bool | `false` |  |
+| backup.extraEnv | list | `[]` |  |
+| backup.extraEnvFrom | list | `[]` |  |
+| backup.failedJobsHistoryLimit | int | `3` |  |
+| backup.local.existingPVC | string | `""` |  |
+| backup.local.mountPath | string | `"/opt/graphdb/backups/"` |  |
+| backup.options.backupSystemData | bool | `true` |  |
+| backup.optionsSecret.existingSecret | string | `""` |  |
+| backup.optionsSecret.secretKey | string | `"backup_options.json"` |  |
+| backup.schedule | string | `"@midnight"` |  |
+| backup.successfulJobsHistoryLimit | int | `3` |  |
+| backup.type | string | `"cloud"` |  |
 | cluster.clusterCreationTimeout | int | `60` |  |
 | cluster.config.configmapKey | string | `"cluster-config.json"` |  |
 | cluster.config.existingConfigmap | string | `""` |  |
@@ -384,7 +397,7 @@ IMPORTANT: This is generated by helm-docs, do not attempt modifying it on hand a
 | ingress.path | string | `""` |  |
 | ingress.pathType | string | `"Prefix"` |  |
 | ingress.tls.enabled | bool | `false` |  |
-| ingress.tls.secretName | string | `nil` |  |
+| ingress.tls.secretName | string | `""` |  |
 | initContainerDataPermissions.enabled | bool | `false` |  |
 | initContainerDataPermissions.securityContext.runAsNonRoot | bool | `false` |  |
 | initContainerDataPermissions.securityContext.runAsUser | int | `0` |  |
@@ -638,6 +651,16 @@ DNS is broken. This is a common issue with Minikube between system restarts or w
 Minikube driver is used. Please refer to
 https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/.
 
+**Filesystem provisioning errors (in Multi-Node Minikube Cluster)**
+
+When expanding your Minikube cluster from one to two or more nodes to deploy different GraphDB
+instances across multiple nodes to ensure high availability, you may encounter errors when
+setting up persistent storage. These issues are due to implementation problems with the storage
+provisioner included with Minikube. To resolve this, you need to adjust your environment accordingly.
+Follow the steps outlined in the official Minikube documentation under the ["CSI Driver and Volume
+Snapshots"](https://minikube.sigs.k8s.io/docs/tutorials/volume_snapshots_and_csi/) section, specifically
+in the "Multi-Node Clusters" chapter.
+
 ## Maintainers
 
 | Name | Email | Url |