Create and use azureFileShare secretName

This document (000020925) is provided subject to the disclaimer at the end of this document.

Resolution

AzureFileShare satisfies the Persistent Volume Claim requirements. To protect the AzureFile credentials, controller.azureFileShare.secretName references a secret. This article demonstrates how to create the secret and links to Microsoft documentation describing the process.

Three helm parameters apply to using AzureFile.

`controller.azureFileShare.enabled`	If true, enable the usage of an existing or statically provisioned Azure File Share	`false`
`controller.azureFileShare.secretName`	The name of the secret containing the Azure file share storage account name and key	`nil`
`controller.azureFileShare.shareName`	The name of the Azure file share to use	`nil`

The above Helm parameters become the following lines in the controller deployment YAML under the volumes section.

azureFile:
secretName: azure-secret
shareName: ShareName

The secretName parameter origin is not apparent but is created from Azure Storage Account Name and Storage Key. Below is an example kubectl command (Variable replacement required.)

kubectl create secret generic azure-secret --from-literal=azurestorageaccountname=$AKS_PERS_STORAGE_ACCOUNT_NAME --from-literal=azurestorageaccountkey=$STORAGE_KEY -n neuvector

More information on managing AzureFileShare and creating the secret can be found at https://docs.microsoft.com/en-us/azure/aks/azure-files-volume#create-a-kubernetes-secret.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.