azure-volume.md

To configure a persistent volume in Azure for storing log files, you can follow these steps using Azure Kubernetes Service (AKS) with an Azure managed disk or Azure file share. Below is an approach for setting up a persistent volume (PV) in Kubernetes backed by Azure Files or Azure Disks.

Steps for Setting Up a Persistent Volume:

1. Create an Azure File Share (for dynamic storage like logs):

Azure Portal:
1. Go to the Azure Storage Account section and create a File Share under the "File shares" section.
2. Note down the Storage Account Name and Storage Account Key, as you'll need them in the next steps.

CLI Command:

az storage account create --resource-group <resource-group-name> --name <storage-account-name> --location <location> --sku Standard_LRS
az storage share create --name <share-name> --account-name <storage-account-name>

2. Create a Kubernetes Secret:

Kubernetes requires credentials to access the Azure file share. Create a Kubernetes secret with the storage account name and key.

kubectl create secret generic azure-secret --from-literal=azurestorageaccountname=<storage-account-name> --from-literal=azurestorageaccountkey=<storage-account-key>

3. Define the Persistent Volume (PV) and Persistent Volume Claim (PVC):

Create a YAML file that defines the PV and PVC using the Azure file share.

apiVersion: v1
kind: PersistentVolume
metadata:
  name: log-pv
spec:
  capacity:
    storage: 5Gi
  accessModes:
    - ReadWriteMany
  azureFile:
    secretName: azure-secret
    shareName: <file-share-name>
    readOnly: false
  persistentVolumeReclaimPolicy: Retain
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: log-pvc
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 5Gi

Apply the file:

kubectl apply -f pv-pvc.yaml

4. Mount the PVC in Your Pod:

Modify your pod or deployment definition to use the PVC for log storage.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: log-app
spec:
  replicas: 1
  selector:
    matchLabels:
      app: log-app
  template:
    metadata:
      labels:
        app: log-app
    spec:
      containers:
      - name: log-container
        image: <your-app-image>
        volumeMounts:
        - name: log-storage
          mountPath: /var/log/app
      volumes:
      - name: log-storage
        persistentVolumeClaim:
          claimName: log-pvc

Apply the deployment:

kubectl apply -f deployment.yaml

5. Verify the Configuration:

Ensure that the PVC is bound to the PV and that the pod is using the Azure file share as expected.

kubectl get pv
kubectl get pvc
kubectl get pods

6. Azure Disk (Alternative Method for Static Log Files):

If you need a block-level storage instead of file share for logs, you can use Azure Disks as persistent storage:

Create a disk with az disk create.
Define a Persistent Volume (PV) using the Azure Disk storage class.
Mount the disk in the same way in the pod as with Azure File Share.

This setup ensures that log files are stored in Azure, persist across pod restarts, and are accessible to all instances if using Azure File Share (with ReadWriteMany access).

Key Considerations:

Azure File Share allows multiple pods to read/write simultaneously.
Azure Disks are suitable for single-node access and high-performance needs.
Ensure you monitor the Azure File Share or Disk capacity to avoid storage exhaustion.

temp3l/azure-volume.md