Backport: Copy platform/administer/node-providers/terraform.mdx to platform_versioned_docs/version-4.5.0/administer/node-providers/terraform.mdx

Author: github-actions[bot]

platform_versioned_docs/version-4.5.0/administer/node-providers/terraform.mdx

@@ -115,6 +115,21 @@ spec:
         }
 ```
 
+### Use quick start templates
+
+Terraform quick-start templates are available to automatically provision the required cloud infrastructure and deploy Kubernetes components such as the [Cloud Controller Manager (CCM)](https://kubernetes.io/docs/concepts/architecture/cloud-controller/) and [Container Storage Interface (CSI)](https://kubernetes.io/blog/2019/01/15/container-storage-interface-ga/).  
+These components enable full cloud provider integration, ensuring that control-plane operations, storage provisioning, and networking features work seamlessly.  
+
+With these templates, you can set up a fully functional environment with minimal manual effort.  
+
+Currently supported providers:  
+
+- [AWS](https://github.com/loft-sh/vcluster-auto-nodes-aws/tree/v0.1.0)  
+- [Azure](https://github.com/loft-sh/vcluster-auto-nodes-azure/tree/v0.1.0)  
+- [GCP](https://github.com/loft-sh/vcluster-auto-nodes-gcp/tree/v0.1.0)  
+
+See the full [quick start deployment guide](/vcluster/next/deploy/worker-nodes/private-nodes/auto-nodes/quick-start-templates) for more details.
+
 ### Available terraform vCluster variables
 
 Besides the user-defined credentials specified below, the platform passes a `var.vcluster` object to each node script. The following values are available:
@@ -131,7 +146,9 @@ Besides the user-defined credentials specified below, the platform passes a `var
 
 [Node types](./overview.mdx) are used by vCluster and the platform to decide what exact machine type should get provisioned. 
 Each node type can define their own node template or reuse the central node type under `spec.nodeType`. 
+<!-- vale off -->
 Properties of node types will be passed via the `var.vcluster.requirements` field to the Terraform script.
+<!-- vale on -->
 
 :::tip Properties
 Use properties of node types to define custom terraform variables which can be used for info like instance type or region.
@@ -282,7 +299,6 @@ data:
 This will lead to the platform passing the Terraform variables `aws_access_key_id` and `aws_secret_access_key` to the `tofu init` and `tofu apply` commands via `-var aws_access_key_id=VALUE`.
 
 ## Terraform backend
-
 By default, the platform will use the [Kubernetes backend](https://developer.hashicorp.com/terraform/language/backend/kubernetes) to store the state of the nodes and node environments in Kubernetes secrets in the `vcluster-platform` namespace. 
 The platform will create a separate workspace per node and node environment in the following form:
 * *Node*: `NODE_CLAIM_NAME.PROJECT_NAME.node`