🔄 synced local 'README.md' with remote 'README.public.md'

README.md

@@ -168,6 +168,10 @@ During the execution of the CLI wizard, the following GCP / Kubernetes resources
   - An IAM Custom Role that is assigned to the IAM Service Account impersonated by Humanitec
   - A Kubernetes Cluster Role on the target cluster, which is bound to the IAM Service Account impersonated by Humanitec
   - A [GKE Cluster Humanitec Resource Definition](https://developer.humanitec.com/integration-and-extensions/containerization/kubernetes/#3-create-a-gke-resource-definition)
+- To let the [Terraform Driver](https://developer.humanitec.com/integration-and-extensions/drivers/generic-drivers/terraform) execute the Terraform code in the [specified cluster](https://developer.humanitec.com/integration-and-extensions/drivers/generic-drivers/terraform/#running-the-terraform-runner-in-a-target-cluster):
+  - A Kubernetes Namespace where the Terraform Runner runs
+  - A Kubernetes Service Account the Terraform Runner runs with
+  - A Kubernetes Role bound to the Terraform Runner Service Account to enable it to deal with the needed resources.
 
 The CLI wizard outputs the name of every GCP resources generated and stores them in the state session.
 
@@ -203,6 +207,10 @@ The CLI wizard assumes that:
 - `ClusterRole` and `ClusterRoleBinding` objects (default name `humanitec-deploy-access`) in the AKS cluster to set up RBAC and workload identity binding.
 - Humanitec Operator and Humanitec Agent are installed in the AKS cluster via Helm charts.
 - Managed Identity (default name `humanitec-operator-identity`) and Federated Credentials to use workload identity to access Azure Key Vault from Humanitec Operator.
+- To let the [Terraform Driver](https://developer.humanitec.com/integration-and-extensions/drivers/generic-drivers/terraform) execute the Terraform code in the [specified cluster](https://developer.humanitec.com/integration-and-extensions/drivers/generic-drivers/terraform/#running-the-terraform-runner-in-a-target-cluster):
+  - A Kubernetes Namespace where the Terraform Runner runs
+  - A Kubernetes Service Account the Terraform Runner runs with
+  - A Kubernetes Role bound to the Terraform Runner Service Account to enable it to deal with the needed resources.
 
 The CLI wizard outputs the name of every Azure resources generated and stores them in the state session.