Monitor and troubleshoot EZswitch in Storage 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

• Ensure the zesty-helm chart is correctly installed.

• Contact Zesty Support for advanced troubleshooting.

References

• Zesty Official Documentation:

  • Kompass Storage

  • Deploy Kompass Storage

• Helm Repositories:

  • zesty-helm (GitHub)

• CLI Plugin:

  • kubectl-zesty plugin (GitHub)