a9s Kubernetes Resources Considerations

This document describes concerns and limitations to be considered when allocating resources for your a9s Kubernetes plans.

Persistent Volumes

When creating Persistent Volumes or Persistent Volume Claims, and the a9s Kubernetes service instance is deleted, the volumes will not be deleted, leaving unclaimed storage usage on the IaaS.

This is also the case when not configuring the reclaim policy for delete, and the volumes still exist after the related Pods are deleted.

When volumes are left, it is necessary manual intervention to delete the volumes on the IaaS.