Hi Femi Fashakin,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
Certainly, if you're running into storage limits with ephemeral storage in Azure Kubernetes Service you can use Persistent Volume Claims (PVCs) instead, PVCs provide a more persistent and scalable storage solution compared to ephemeral storage.
Persistent storage is designed for data that must outlast a Pod's lifecycle and is managed through Persistent Volumes (PVs) and Persistent Volume Claims (PVCs). It ensures that data remains intact even if the Pod is deleted or restarted, operates independently of the Pod's lifecycle, and can be dynamically provisioned and scaled as needed. This type of storage is ideal for databases, application state, and other critical data.
First define a StorageClass to specify the type of storage (e.g., Azure Disk). Then, create a PVC to request storage with specific requirements (e.g., size, access mode). AKS dynamically provisions a PV to satisfy the PVC. Mount the PVC into a Pod as a volume. Data written to the PVC persists across Pod restarts and deletions.
For your reference: How to Manage Kubernetes Persistent Volume Claims Effectively
Persistent volumes
If you have any further queries, please do let us know. If the answer is helpful, please click "Accept Answer" and "Upvote it".