mirror of https://github.com/dapr/docs.git
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>
This commit is contained in:
parent
7c40430f03
commit
178e0c8a77
|
@ -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" %}}
|
||||
|
|
Loading…
Reference in New Issue