Mounting an External Azure Storage Account with AKS Cluster: A Step-by-Step Guide

Prerequisites

Before we begin, ensure you have the following:

• A running AKS cluster (version 1.18 or later)
• An Azure storage account (general-purpose v2 or blob storage)
• Azure CLI installed and configured on your machine
• Kubernetes CLI (kubectl) installed and configured on your machine
• Basic knowledge of Kubernetes and Azure storage concepts

Step 1: Create an Azure Storage Account and Container

Create an Azure storage account and a container to store your data. You can do this using the Azure portal or Azure CLI. For this example, we’ll use the Azure CLI:

az storage account create --name  --resource-group  --location  --sku Standard_LRS

az storage container create --name  --account-name  --resource-group 

Replace , , , and with your desired values.

Step 2: Create an Azure Storage Account Key and Access Secret

Create a storage account key and access secret to authenticate with your storage account. You can do this using the Azure portal or Azure CLI:

az storage account keys list --account-name  --resource-group 

az storage account show-connection-string --account-name  --resource-group 

Take note of the storage account key and connection string; you’ll need them later.

Step 3: Create a Kubernetes Secret

Create a Kubernetes secret to store your Azure storage account key and access secret. You can do this using kubectl:

kubectl create secret generic azure-storage-secret --from-literal=AZURE_STORAGE_ACCOUNT_KEY= --from-literal=AZURE_STORAGE_CONNECTION_STRING=

Replace and with the values from Step 2.

Step 4: Create a Kubernetes StorageClass

Create a Kubernetes StorageClass to define the storage type and parameters for your external storage. You can do this using kubectl:

kubectl apply -f - <
  storageAccount: 
  storageAccountKey: $(AZURE_STORAGE_ACCOUNT_KEY)
  storageAccountConnectionString: $(AZURE_STORAGE_CONNECTION_STRING)
EOF

Replace , , , and with the values from previous steps.

Step 5: Create a Kubernetes Persistent Volume (PV)

Create a Kubernetes Persistent Volume (PV) to represent the external storage account. You can do this using kubectl:

kubectl apply -f - <
      diskURI: https://.blob.core.windows.net//.vhd
EOF

Replace , , and with your desired values.

Step 6: Create a Kubernetes Persistent Volume Claim (PVC)

Create a Kubernetes Persistent Volume Claim (PVC) to request storage resources from the PV. You can do this using kubectl:

kubectl apply -f - <
Step 7: Mount the External Storage Account with AKS Cluster
Mount the external storage account with your AKS cluster by creating a Kubernetes Pod that uses the PVC. You can do this using kubectl:
kubectl apply -f - <
Verify that the Pod is running and the external storage account is mounted by checking the Pod's logs:
kubectl logs -f azure-storage-pod

Conclusion
And that's it! You've successfully mounted an external Azure storage account with your AKS cluster. This setup provides a flexible and scalable storage solution for your Kubernetes workloads. Remember to adjust the storage class, PV, and PVC to fit your specific needs.



Step
Description


1
Create an Azure storage account and container


2


3
Create a Kubernetes secret


4
Create a Kubernetes StorageClass


5
Create a Kubernetes Persistent Volume (PV)


6
Create a Kubernetes Persistent Volume Claim (PVC)


7
Mount the external storage account with AKS cluster


Troubleshooting Tips

Verify that your Azure storage account and container are accessible and have the correct permissions.
Check that your Kubernetes secret is correctly created and referenced in your StorageClass.
Ensure that your StorageClass and PV are correctly defined and referenced in your PVC.
Verify that your Pod is running and the external storage account is mounted by checking the Pod's logs.

By following these steps, you've successfully mounted an external Azure storage account with your AKS cluster. This setup provides a powerful and flexible storage solution for your Kubernetes workloads. Happy deploying!
Frequently Asked Questions
Get the scoop on mounting an external Azure storage account with an AKS cluster!


What is the main reason to mount an external Azure storage account with an AKS cluster?

The primary reason is to persist data even if the AKS cluster is deleted or scaled down. By mounting an external storage account, you can decouple your data from the cluster's lifecycle, ensuring that your data remains safe and accessible.



What type of Azure storage account is recommended for mounting with an AKS cluster?

A general-purpose v2 storage account is the recommended option. This type of account provides the most flexibility and features, including support for Blob Storage, File Storage, and Data Lake Storage.



How do I mount an external Azure storage account to an AKS cluster?

You can mount an external Azure storage account using the Azure Files or Azure Blob Storage CSI (Container Storage Interface) driver. This involves creating a storage class, a persistent volume claim, and a pod that uses the persistent volume claim to access the storage account.



What are the benefits of using a CSI driver to mount an external Azure storage account with an AKS cluster?

Using a CSI driver provides a standardized way to interact with external storage systems, allowing for easy integration and management of storage resources. It also enables features like dynamic provisioning, volume cloning, and snapshots, making it easier to manage and scale your storage needs.



Are there any security considerations when mounting an external Azure storage account with an AKS cluster?

Yes, it's essential to secure your storage account and access keys to prevent unauthorized access. Use Azure Active Directory (AAD) authentication, Azure role-based access control (RBAC), and encryption to protect your data and access credentials.



Share this: