From 178e0c8a7725d25cbad150cd34e03c414258be6c Mon Sep 17 00:00:00 2001
From: Jake Engelberg <152900222+jake-engelberg@users.noreply.github.com>
Date: Mon, 3 Mar 2025 17:44:05 -0500
Subject: [PATCH] Update kubernetes-persisting-scheduler.md (#4568)

dapr / PVC uninstall specifics, about how a manual deletion of PVCs is required to define a new volume.

Signed-off-by: Jake Engelberg <152900222+jake-engelberg@users.noreply.github.com>
---
 .../hosting/kubernetes/kubernetes-persisting-scheduler.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-persisting-scheduler.md b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-persisting-scheduler.md
index 552331bd1..d6c187b19 100644
--- a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-persisting-scheduler.md
+++ b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-persisting-scheduler.md
@@ -69,6 +69,14 @@ helm upgrade --install dapr dapr/dapr \
 {{% /codetab %}}
 {{< /tabs >}}
 
+{{% alert title="Note" color="primary" %}}
+For storage providers that do NOT support dynamic volume expansion: If Dapr has ever been installed on the cluster before, the Scheduler's Persistent Volume Claims must be manually uninstalled in order for new ones with increased storage size to be created.
+```bash
+kubectl delete pvc -n dapr-system dapr-scheduler-data-dir-dapr-scheduler-server-0 dapr-scheduler-data-dir-dapr-scheduler-server-1 dapr-scheduler-data-dir-dapr-scheduler-server-2
+```
+Persistent Volume Claims are not deleted automatically with an [uninstall]({{< ref dapr-uninstall.md >}}). This is a deliberate safety measure to prevent accidental data loss.
+{{% /alert %}}
+
 #### Increase existing Scheduler Storage Size
 
 {{% alert title="Warning" color="warning" %}}