put the labels back

Author: renetapopova

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

@@ -321,7 +321,7 @@ The following are examples of how to configure the backup system for different S
 ----
 neo4j:
   image: "neo4j/helm-charts-backup"
-  imageTag: "5.14.0"
+  imageTag: "5.26.0"
   jobSchedule: "* * * * *"
   successfulJobsHistoryLimit: 3
   failedJobsHistoryLimit: 1
@@ -359,7 +359,7 @@ backup:
 ======
 [.include-with-legacy-MinIO-support]
 ======
-[role=label--deprecated-5.26]
+[role=label--new-5.14 label--deprecated-5.26]
 .Legacy MinIO support
 [source, yaml]
 ----
@@ -383,12 +383,10 @@ backup:
 * Legacy MinIO support through the `minioEndpoint` parameter is deprecated - use `s3Endpoint` instead.
 ====
 
-
+[role=label--new-5.16]
 [[kubernetes-neo4j-backup-on-prem]]
 == Prepare to back up a database(s) to on-premises storage
 
-_This feature is available from Neo4j 5.16._
-
 You can perform a backup of a Neo4j database(s) to on-premises storage using the _neo4j/neo4j-admin_ Helm chart.
 When configuring the _backup-values.yaml_ file, keep the “cloudProvider” field empty and provide a persistent volume in the `tempVolume` section to ensure the backup files are persistent if the pod is deleted.