Moving TPU v6 from community to core

Author: shubpal07

community/examples/gke-tpu-v6/README.md examples/gke-tpu-v6/README.mdcommunity/examples/gke-tpu-v6/README.md renamed to examples/gke-tpu-v6/README.md

@@ -1,6 +1,6 @@
 # GKE TPU V6 blueprint
 
-This example shows how a TPU cluster with v6 machines and topology 4x4 can be created. The example also includes a `tpu-available-chips.yaml` that creates a kubernetes service and job. The job includes commands to install `jax` and run a simple command using jax, on the TPU.
+This example shows how a TPU cluster with v6 machines and topology 4x4 can be created. The example also includes a `tpu-multislice.yaml` that creates a kubernetes service and job. The job includes commands to install `jax` and run a simple command using jax, on the TPU.
 
 Key parameters when working with TPUs:
 
@@ -59,7 +59,7 @@ This section guides you through the cluster creation process, ensuring that your
    * `BUCKET_NAME`: the name of the new Cloud Storage bucket.
    * `COMPUTE_REGION`: the compute region where you want to store the state of the Terraform deployment.
 
-1. In the [`community/examples/gke-tpu-v6/gke-tpu-v6-deployment.yaml`](https://github.com/GoogleCloudPlatform/cluster-toolkit/blob/main/community/examples/gke-tpu-v6/gke-tpu-v6-deployment.yaml) file, replace the following variables in the `terraform_backend_defaults` and `vars` sections to match the specific values for your deployment:
+1. In the [`examples/gke-tpu-v6/gke-tpu-v6-deployment.yaml`](https://github.com/GoogleCloudPlatform/cluster-toolkit/blob/main/examples/gke-tpu-v6/gke-tpu-v6-deployment.yaml) file, replace the following variables in the `terraform_backend_defaults` and `vars` sections to match the specific values for your deployment:
 
    * `bucket`: the name of the Cloud Storage bucket you created in the previous step.
    * `project_id`: your Google Cloud project ID.
@@ -72,10 +72,10 @@ This section guides you through the cluster creation process, ensuring that your
    * `authorized_cidr`: The IP address range that you want to allow to connect with the cluster. This CIDR block must include the IP address of the machine to call Terraform.
    * `reservation`: the name of the compute engine reservation of TPU v6 nodes.
 
-    To modify advanced settings, edit `community/examples/gke-tpu-v6/gke-tpu-v6.yaml`.
+    To modify advanced settings, edit `examples/gke-tpu-v6/gke-tpu-v6.yaml`.
 
 1. To use on-demand capacity, you can remove the reservation usage by making the following changes.
-   1. Remove the `reservation` variable from the [`gke-tpu-v6-deployment.yaml`](https://github.com/GoogleCloudPlatform/cluster-toolkit/blob/main/community/examples/gke-tpu-v6/gke-tpu-v6-deployment.yaml) file.
+   1. Remove the `reservation` variable from the [`gke-tpu-v6-deployment.yaml`](https://github.com/GoogleCloudPlatform/cluster-toolkit/blob/main/examples/gke-tpu-v6/gke-tpu-v6-deployment.yaml) file.
    1. Remove the `reservation_affinity` block from the nodepool module.
 
 1. Generate [Application Default Credentials (ADC)](https://cloud.google.com/docs/authentication/provide-credentials-adc#google-idp) to provide access to Terraform.
@@ -86,8 +86,8 @@ This section guides you through the cluster creation process, ensuring that your
    ```sh
     cd ~/cluster-toolkit
     ./gcluster deploy -d \
-    community/examples/gke-tpu-v6/gke-tpu-v6-deployment.yaml \
-    community/examples/gke-tpu-v6/gke-tpu-v6.yaml
+    examples/gke-tpu-v6/gke-tpu-v6-deployment.yaml \
+    examples/gke-tpu-v6/gke-tpu-v6.yaml
    ```
 
 ## Advanced Blueprint: GKE TPU with GCS Integration
@@ -109,15 +109,15 @@ The process is nearly identical to the basic deployment.
     ```sh
     cd ~/cluster-toolkit
     ./gcluster deploy -d \
-    community/examples/gke-tpu-v6/gke-tpu-v6-deployment.yaml \
-    community/examples/gke-tpu-v6/gke-tpu-v6-advanced.yaml
+    examples/gke-tpu-v6/gke-tpu-v6-deployment.yaml \
+    examples/gke-tpu-v6/gke-tpu-v6-advanced.yaml
     ```
 
 1. After deployment, the blueprint will output instructions for running a fio benchmark job. This job serves as a validation test to confirm that the GCS mounts are working correctly for both reading and writing. Follow the printed instructions to run the test.
 
 ## Run the sample job
 
-The [tpu-available-chips.yaml](https://github.com/GoogleCloudPlatform/cluster-toolkit/blob/main/community/examples/gke-tpu-v6/tpu-available-chips.yaml) file creates a service and a job resource in kubernetes. It is based on https://cloud.google.com/kubernetes-engine/docs/how-to/tpus#tpu-chips-node-pool. The  workload returns the number of TPU chips across all of the nodes in a multi-host TPU slice.
+The [tpu-multislice.yaml](https://github.com/GoogleCloudPlatform/cluster-toolkit/blob/main/examples/gke-tpu-v6/tpu-multislice.yaml) file creates a service and a job resource in kubernetes. It is based on https://cloud.google.com/kubernetes-engine/docs/how-to/tpus#tpu-chips-node-pool. The  workload returns the number of TPU chips across all of the nodes in a multi-host TPU slice.
 
 1. Connect to your cluster:
 
@@ -127,7 +127,7 @@ The [tpu-available-chips.yaml](https://github.com/GoogleCloudPlatform/cluster-to
 
     Replace the `REGION` and `PROJECT_ID` with the ones used in the blueprint.
 
-1. Update the nodeSelector under the template spec of tpu-available-chips.yaml file. The values depend on the tpu accelerator and tpu topology used in the blueprint.
+1. Update the nodeSelector under the template spec of tpu-multislice.yaml file. The values depend on the tpu accelerator and tpu topology used in the blueprint.
 
     ```yaml
     nodeSelector:
@@ -138,7 +138,7 @@ The [tpu-available-chips.yaml](https://github.com/GoogleCloudPlatform/cluster-to
 1. Create the resources:
 
     ```sh
-    kubectl create -f ~/cluster-toolkit/community/examples/gke-tpu-v6/tpu-multislice.yaml
+    kubectl create -f ~/cluster-toolkit/examples/gke-tpu-v6/tpu-multislice.yaml
     ```
 
     This command returns a service and a job name.

…ples/gke-tpu-v6/gke-tpu-v6-advanced.yaml …ples/gke-tpu-v6/gke-tpu-v6-advanced.yamlcommunity/examples/gke-tpu-v6/gke-tpu-v6-advanced.yaml renamed to examples/gke-tpu-v6/gke-tpu-v6-advanced.yaml community/examples/gke-tpu-v6/gke-tpu-v6-advanced.yaml renamed to examples/gke-tpu-v6/gke-tpu-v6-advanced.yaml

@@ -120,7 +120,7 @@ check_background() {
 	fi
 }
 
-CONFIGS=$(find examples/ community/examples/ tools/validate_configs/test_configs/ docs/tutorials/ docs/videos/build-your-own-blueprint/ -name "*.yaml" -type f -not -path 'examples/machine-learning/a3-megagpu-8g/*' -not -path 'examples/machine-learning/a3-ultragpu-8g/*' -not -path 'examples/machine-learning/build-service-images/*' -not -path 'examples/gke-a3-ultragpu/*' -not -path 'examples/hypercompute_clusters/*' -not -path 'examples/gke-consumption-options/*' -not -path 'examples/gke-a4/*' -not -path 'examples/gke-a3-megagpu/*' -not -path 'examples/machine-learning/a4-highgpu-8g/*' -not -path 'examples/machine-learning/a4x-highgpu-4g/*' -not -path 'community/examples/gke-tpu-v6/*' -not -path 'community/examples/xpk-n2-filestore/*' -not -path 'examples/gke-a4x/*' -not -path 'examples/science/af3-slurm/*' -not -path 'examples/gke-h4d/*' -not -path 'community/examples/hpc-slinky/*' -not -path 'examples/gke-g4/*' -not -path 'community/examples/slurm-gke/*' -not -path 'examples/hpc-slurm-h4d/*' -not -path 'examples/machine-learning/a3-highgpu-8g/*' -not -path 'examples/netapp-volumes.yaml' -not -path 'examples/gke-tpu-7x/*')
+CONFIGS=$(find examples/ community/examples/ tools/validate_configs/test_configs/ docs/tutorials/ docs/videos/build-your-own-blueprint/ -name "*.yaml" -type f -not -path 'examples/machine-learning/a3-megagpu-8g/*' -not -path 'examples/machine-learning/a3-ultragpu-8g/*' -not -path 'examples/machine-learning/build-service-images/*' -not -path 'examples/gke-a3-ultragpu/*' -not -path 'examples/hypercompute_clusters/*' -not -path 'examples/gke-consumption-options/*' -not -path 'examples/gke-a4/*' -not -path 'examples/gke-a3-megagpu/*' -not -path 'examples/machine-learning/a4-highgpu-8g/*' -not -path 'examples/machine-learning/a4x-highgpu-4g/*' -not -path 'community/examples/gke-tpu-v6/*' -not -path 'community/examples/xpk-n2-filestore/*' -not -path 'examples/gke-a4x/*' -not -path 'examples/science/af3-slurm/*' -not -path 'examples/gke-h4d/*' -not -path 'community/examples/hpc-slinky/*' -not -path 'examples/gke-g4/*' -not -path 'community/examples/slurm-gke/*' -not -path 'examples/hpc-slurm-h4d/*' -not -path 'examples/machine-learning/a3-highgpu-8g/*' -not -path 'examples/netapp-volumes.yaml' -not -path 'examples/gke-tpu-7x/*' -not -path 'examples/gke-tpu-v6/*')
 # Exclude blueprints that use v5 modules.
 declare -A EXCLUDE_EXAMPLE
 EXCLUDE_EXAMPLE["tools/validate_configs/test_configs/two-clusters-sql.yaml"]=