Enhancing MySQL Storage Expansion Documentation

docs/deploy/aws.md

@@ -187,6 +187,49 @@ Note down the elb address in the address column. Add the DNS CNAME record to the
 from above) to the elb address. DNS updates generally take a few minutes to an hour. Once that is done, you should be
 able to access datahub-frontend through the host-name.
 
+## Increasing MySQL Storage in Kubernetes
+
+### Kubernetes Configuration
+
+To increase MySQL storage in a Kubernetes environment, you need to modify the `values.yaml` file for persistent volume claims (PVCs) and redeploy the application. Here is an example configuration:
+
+```yaml
+mysql:
+  enabled: true
+  primary:
+    resources:
+      requests:
+        cpu: 100m
+        memory: 1024Mi
+      limits:
+        cpu: 200m
+        memory: 2048Mi
+    persistence:
+      size: 16Gi
+```
+
+After updating the `values.yaml`, apply the changes using Helm:
+
+```
+helm upgrade --install datahub datahub/datahub --values values.yaml
+```
+
+### Data Integrity
+
+Before resizing, ensure data integrity by taking backups. This is crucial to prevent data loss during the resizing process.
+
+### Cluster Environment Variations
+
+The steps to resize PVCs can differ based on the cluster environment (e.g., AWS, GCP, Azure, on-premises). Some environments support dynamic resizing of PVCs, while others require manual intervention.
+
+### Helm Charts
+
+Ensure that Helm charts reflect the changes in storage size and upgrade the Helm release properly.
+
+### Real-world Examples
+
+In a real-world scenario, a user resolved a MySQL storage issue by increasing the PVC size and redeploying. They updated their `values.yaml` file to specify the desired storage size and redeployed the MySQL prerequisites.
+
 ## Use AWS managed services for the storage layer
 
 Managing the storage services like MySQL, Elasticsearch, and Kafka as kubernetes pods requires a great deal of