---
title: "Maintain PV autoscaling"
slug: "maintain-pvs-autoscaling"
updated: 2026-07-20T09:54:11Z
published: 2026-07-20T09:54:11Z
canonical: "docs.zesty.co/maintain-pvs-autoscaling"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zesty.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Maintain PV autoscaling

This topic describes how to perform the following maintenance operations:

- [Delete workloads](/v1/docs/maintain-pvs-autoscaling#delete-workloads)
- [Upgrade components](/v1/docs/maintain-pvs-autoscaling#to-upgrade-components)
- [Uninstall PV Autoscaling](/v1/docs/maintain-pvs-autoscaling#uninstall-variablek8s)

### Delete workloads

The following rules apply to deleting:

1. Deleting the workload is the same as native K8s components:
  - If configured with *WhenDeleted: Delete*, the connected resources will be deleted.
  - If not configured that way, no further resources are deleted.
2. The Zesty PVC deletion process is as follows:
  - If the value of *ReclaimPolicy* is *delete*, the dummy PVC is deleted, and this triggers the deletion of the Filesystem and related PVCs and PVs.
  - If the value of *ReclaimPolicy* is *retain*, no further deletions occur, and the dummy PV (and its corresponding resources) stays intact.

### Upgrade components

If you ever upgrade your cluster, you must be sure to upgrade PV autoscaling afterwards.

#### To upgrade components:

- Run these commands:

```plaintext
helm repo update
helm upgrade zesty-pvc zestyrepo/zesty
```

### Uninstall PV autoscaling

You can perform a Helm uninstall only if there are no Filesystems of the Zesty storage class in the cluster. This is because uninstalling PV autoscaling components causes the native Pod migration of K8s to stop working,

#### To uninstall PV autoscaling:

- Run the following command: `helm uninstall/delete zesty-pvc -name=<namespace>`

The `-name=<namespace> - argument `is optional, needed only if PV autoscaling is installed on a dedicated namespace.

During the uninstallation, Zesty runs a Pod named “zesty-pvc-assert-uninstall-pre-delete-job” which runs pre-uninstallation validations. If the validations failed, this Pod will stay alive so its logs can be reviewed for further analysis.