In AKS, you can use Azure Disks or Azure Files to provide the Persistent Volume. This is often used in conjunction with the aptly named StatefulSets.
This article outlines these data management considerations in detail and how to work around Azure Files limitation to achieve feature parity with using Azure Managed Disks.īefore we walk you through how to automate Azure Files restore in AKS snapshots, let’s quickly touch on some of the important underlying concepts: Persistent VolumeĪ Persistent Volume (PV) is a storage resource created and managed by the Kubernetes API that can exist beyond the lifetime of an individual pod. We've created a client object to the blob with our URI.If you are considering Azure Files as the persistent storage for your Azure Kubernetes Service (AKS) applications, there are important considerations around AKS backup and recovery with implications on how you can perform Dev, Test, and Staging.We've created a variable to our Disk URI path.We've set variables that set our Account and Key to the Blob Storage.With the "Add Type" command, we've added a reference to the DLL that represents the Azure API to us.$blobClient = New-Object ( $blobPath, $creds ) $blobPath = " " $creds = New-Object ( $AzureAccountName, $AzureAccountKey ) $AzureAccountName = " MyStorageAccountName " $AzureAccountKey = " MyStorageAccountKey "
To get the Disk URI, we will go to our Blob Storage and then "Containers" in the Classic Azure Portal:Īdd-Type -Path ' C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.4\bin\ ' Second, you need your Blob Storage Account's username and password: In Microsoft Azure, this function is not a simple "right click, take snapshot" issue, but with some PowerShell magic, it's still possible.įirst, you require the Microsoft Azure SDK: SDK Usually, one of the most valuable functions in a virtual environment is taking snapshots.
0 kommentar(er)
