Add support for adding nodeSelector labels with neo4j-admin helm (#937) (#938)

Cherry-picked from #937

Author: renetapopova

modules/ROOT/pages/kubernetes/operations/backup-restore.adoc

@@ -204,7 +204,9 @@ The _neo4j/neo4j-admin_ Helm chart installs a cronjob that launches a pod based
 [[kubernetes-neo4j-backup-parameters]]
 === Backup parameters
 
-To see what options are configurable on the Helm chart use `helm show values` and the Helm chart _neo4j/neo4j-admin_.
+To see what options are configurable on the Helm chart use `helm show values` and the Helm chart _neo4j/neo4j-admin_. +
+From version 5.10, the _neo4j/neo4j-admin_ Helm chart also supports assigning your Neo4j pods to specific nodes using `nodeSelector` labels.
+For more information, see xref:kubernetes/operations/assign-neo4j-pods.adoc[Assigning backup pods to specific nodes].
 For example:
 
 [source, shell, role='noheader']
@@ -304,9 +306,6 @@ backup:
   #Below are all neo4j-admin database backup flags / options
   #To know more about the flags read here : https://neo4j.com/docs/operations-manual/current/backup-restore/online-backup/
   pageCache: ""
-  fallbackToFull: true
-  removeExistingFiles: true
-  removeBackupFiles: true
   includeMetadata: "all"
   type: "AUTO"
   keepFailed: false
@@ -354,6 +353,12 @@ resources:
     ephemeralStorage: "4Gi"
   limits:
     ephemeralStorage: "5Gi"
+
+# nodeSelector labels
+# please ensure the respective labels are present on one of nodes or else helm charts will throw an error
+nodeSelector: {}
+#  label1: "true"
+#  label2: "value1"
 ----
 
 [[kubernetes-neo4j-restore]]