finally got postgres working with a custom storage class

Author: DougAnsonAustinTX

content/learning-paths/servers-and-cloud-computing/helm-on-gcp/gke-cluster-for-helm.md

@@ -142,6 +142,58 @@ gke-helm-arm64-cluster-default-pool-f4ab8a2d-5ldp   Ready    <none>   5h54m   v1
 
 All nodes should be in **Ready** state and the Kubernetes control plane should be accessible.
 
+### Taint the cluster nodes
+
+Taint the nodes to ensure proper scheduling. For each node starting with **gke**, run the taint command. For example: 
+
+```console
+kubectl taint nodes gke-helm-arm64-cluster-default-pool-f4ab8a2d-5h6f kubernetes.io/arch=arm64:NoSchedule-
+kubectl taint nodes gke-helm-arm64-cluster-default-pool-f4ab8a2d-5ldp kubernetes.io/arch=arm64:NoSchedule-
+```
+
+Replace the node names with your actual node names from the previous command output.
+
+### Create hyperdisk storage class for our cluster
+
+In order to use the c4a architecture with our cluster, a new storage class must be created. 
+
+Create a new file, hyperdisk.yaml, with this content:
+```yaml
+apiVersion: storage.k8s.io/v1
+kind: StorageClass
+metadata:
+  name: my-hyperdisk-sc
+provisioner: pd.csi.storage.gke.io
+parameters:
+  type: hyperdisk-balanced # Or hyperdisk-ssd, etc.
+reclaimPolicy: Delete
+volumeBindingMode: WaitForFirstConsumer
+```
+
+Apply the hyperdisk.yaml file to the cluster:
+
+```console
+kubectl apply -f ./hyperdisk.yaml
+```
+
+Confirm that the new storage class has been added:
+
+```console
+kubectl get storageclass
+```
+
+The output should contain the new **my-hyperdisk-sc** storage class:
+
+```output
+NAME                     PROVISIONER             RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
+my-hyperdisk-sc          pd.csi.storage.gke.io   Delete          WaitForFirstConsumer   false                  7m27s
+premium-rwo              pd.csi.storage.gke.io   Delete          WaitForFirstConsumer   true                   20m
+standard                 kubernetes.io/gce-pd    Delete          Immediate              true                   20m
+standard-rwo (default)   pd.csi.storage.gke.io   Delete          WaitForFirstConsumer   true                   20m
+```
+
+The new storage class will be used in the next section. 
+
 ## What you've accomplished and what's next
 
 You've successfully prepared your GKE environment by installing and configuring the Google Cloud SDK, creating a GKE cluster, connecting kubectl to the cluster, and verifying cluster access. Your environment is now ready to deploy applications using Helm charts.

content/learning-paths/servers-and-cloud-computing/helm-on-gcp/postgresql-helm.md

@@ -105,7 +105,7 @@ This approach prevents hard-coding credentials and follows Kubernetes security b
 
 ### Create pvc.yaml
 
-Create `my-postgres/templates/pvc.yaml` with the following content to request persistent storage so PostgreSQL data remains available even if the pod restarts:
+Create `my-postgres/templates/pvc.yaml` with the following content to request persistent storage so PostgreSQL data remains available even if the pod restarts. Note the specification of the storage class that will be used **my-hyperdisk-sc** which was created and added to our cluster in the previous section. This hyperdisk-based storage class is required for the c4a architecture:
 
 ```yaml
 apiVersion: v1
@@ -115,6 +115,7 @@ metadata:
 spec:
   accessModes:
     - ReadWriteOnce
+  storageClassName: my-hyperdisk-sc
   resources:
     requests:
       storage: {{ .Values.persistence.size }}
@@ -211,31 +212,6 @@ REVISION: 1
 TEST SUITE: None
 ```
 
-### Taint the nodes
-
-Taint the nodes to ensure proper scheduling. First, list the nodes:
-
-```console
-kubectl get nodes
-```
-
-The output is similar to:
-
-```output
-NAME                                                STATUS   ROLES    AGE   VERSION
-gke-helm-arm64-cluster-default-pool-7400f0d3-dq80   Ready    <none>   10m   v1.33.5-gke.2072000
-gke-helm-arm64-cluster-default-pool-7400f0d3-v3c9   Ready    <none>   10m   v1.33.5-gke.2072000
-```
-
-For each node starting with **gke**, run the taint command. For example: 
-
-```console
-kubectl taint nodes gke-helm-arm64-cluster-default-pool-7400f0d3-dq80 kubernetes.io/arch=arm64:NoSchedule-
-kubectl taint nodes gke-helm-arm64-cluster-default-pool-7400f0d3-v3c9 kubernetes.io/arch=arm64:NoSchedule-
-```
-
-Replace the node names with your actual node names from the previous command output. 
-
 ### Check the runtime status
 
 Check the pod and PVC status: