Skip to content

Commit 178e0c8

Browse files
authoredMar 3, 2025··
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 <[email protected]>
1 parent 7c40430 commit 178e0c8

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed
 

‎daprdocs/content/en/operations/hosting/kubernetes/kubernetes-persisting-scheduler.md

+8
Original file line numberDiff line numberDiff line change
@@ -69,6 +69,14 @@ helm upgrade --install dapr dapr/dapr \
6969
{{% /codetab %}}
7070
{{< /tabs >}}
7171

72+
{{% alert title="Note" color="primary" %}}
73+
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.
74+
```bash
75+
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
76+
```
77+
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.
78+
{{% /alert %}}
79+
7280
#### Increase existing Scheduler Storage Size
7381

7482
{{% alert title="Warning" color="warning" %}}

0 commit comments

Comments
 (0)
Please sign in to comment.