Update README with GKE parallelstore related example blueprint details

examples/README.md

@@ -1518,6 +1518,30 @@ cleaned up when the job is deleted.
 
 [storage-gke.yaml]: ../examples/storage-gke.yaml
 
+### [gke-storage-parallelstore.yaml] ![core-badge] ![experimental-badge]
+
+This blueprint shows how to use parallelstore storage options with GKE in the toolkit.
+
+The blueprint contains the following:
+
+* A K8s Job that uses a parallelstore storage volume option.
+* A K8s Job that demonstrates ML training workload with parallelstore storage disk ops.
+
+> **Warning**: In this example blueprint, when storage type `Parallelstore` is specified in `gke-storage` module.
+> The lifecycle of the parallelstore is managed by the blueprint.
+> On glcuster destroy ops, the Parallelstore storage created will also be destroyed.
+>
+> [!Note]
+> The Kubernetes API server will only allow requests from authorized networks.
+> The `gke-cluster` module needs access to the Kubernetes API server
+> to create a Persistent Volume and a Persistent Volume Claim. **You must use
+> the `authorized_cidr` variable to supply an authorized network which contains
+> the IP address of the machine deploying the blueprint, for example
+> `--vars authorized_cidr=<your-ip-address>/32`.** You can use a service like
+> [whatismyip.com](https://whatismyip.com) to determine your IP address.
+
+[gke-storage-parallelstore.yaml]: ../examples/gke-storage-parallelstore.yaml
+
 ### [gke-a3-megagpu.yaml] ![core-badge] ![experimental-badge]
 
 This blueprint shows how to provision a GKE cluster with A3 Mega machines in the toolkit.