Add a callout to point out that some files may have already been crea…

…ted if the `deployer generate dedicated-cluster` command was used

docs/hub-deployment-guide/deploy-support/configure-support.md

@@ -6,6 +6,12 @@ These tools are [`ingress-nginx`](https://kubernetes.github.io/ingress-nginx/),
 
 This section will walk you through how to deploy the support chart on a cluster.
 
+```{attention}
+If you ran `deployer generate dedicated-cluster ...` during the [new cluster setup](new-cluster),
+then a lot of these files will have already been created for you and you do not
+need to recreate them, only update them if required.
+```
+
 ## Create a `support.values.yaml` file in your chosen cluster folder
 
 In the `infrastructure` repo, the full filepath should be: `config/clusters/<cluster_name>/support.values.yaml`.

docs/hub-deployment-guide/deploy-support/register-central-grafana.md

@@ -2,6 +2,12 @@
 
 Once you have [deployed the support chart](deploy-support-chart), you must also register this cluster as a datasource for the [central Grafana dashboard](grafana-dashboards:central). This will allow you to visualize cluster statistics not only from the cluster-specific Grafana deployment but also from the central dashboard, that aggregates data from all the clusters.
 
+```{attention}
+If you ran `deployer generate dedicated-cluster ...` during the [new cluster setup](new-cluster),
+then a lot of these files will have already been created for you and you do not
+need to recreate them, only update them if required.
+```
+
 ## Create a `support.secret.values.yaml` file
 
 Only 2i2c staff and our centralized grafana should be able to access the prometheus data on a cluster from outside the cluster.