---
title: "Monitor and troubleshoot EZswitch in PV autoscaling"
slug: "monitor-and-troubleshoot-ezswitch-in-storage-autoscaling"
updated: 2026-07-21T09:45:50Z
published: 2026-07-21T09:45:50Z
canonical: "docs.zesty.co/monitor-and-troubleshoot-ezswitch-in-storage-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.

# Monitor and troubleshoot EZswitch in PV autoscaling

This topic describes monitoring and troubleshooting steps for EZswitchEZswitch.

## Log and monitor

The EZswitch controller (zesty-ezswitch-controller) runs in the ezswitch namespace.

- **To view logs**: `kubectl logs deploy/zesty-ezswitch-controller -n ezswitch`
- **To check EZswitch events and status**: `kubectl describe ezswitch myapp-sts`

**Note**: Unlike Kompass Storage, there is no dedicated Prometheus exporter for EZswitch.

## GitOps and Version Control

For GitOps workflows (e.g., Argo CD), commit EZswitch resources to a Git repository. Start with autoMigrate=false and later push a commit changing it to true to trigger the final switchover. This ensures changes are tracked, reviewed, and rolled out through a GitOps process.

## Troubleshooting

If any issues occur, use abort or rollback to halt or revert the process.

- Check the [controller logs](/docs/monitor-and-troubleshoot-ezswitch-in-storage-autoscaling#bookmark=id.tyjcwt)
- Ensure the [zesty-helm](https://github.com/zesty-co/zesty-helm) chart is correctly installed.
- Contact Zesty Support for advanced troubleshooting.

## References

- **Zesty documentation**:
  - [PV Autoscaling](/v1/docs/storage-optimization)
  - [Deploy PV autoscaling](/v1/docs/deploy-storage-autoscaling)
- **Helm repositories**:
  - [zesty-helm (GitHub)](https://github.com/zesty-co/zesty-helm)
- **CLI plugin**:
  - [kubectl-zesty plugin (GitHub)](https://github.com/zesty-co/kubectl-plugin)