failed to initialize new pipeline [failed to authenticate credentials for azstorage]

Gyan Prakash Rai 0 Reputation points
2024-10-18T11:02:56.1066667+00:00
  1. I have created a storage account (StorageV2 (general purpose v2)) and a container inside it.
  2. This storage account have both .blob.core.windows.net/ and .dfs.core.windows.net/ private end points. Public Network access is disabled.
  3. Access Key authentication is being used.
  4. Created a PV for this storage account and PVC by using blob.csi.azure.com storage class driver.
  5. Created a deployment to deploy the pod attaching the PVC.

Now, when deploying the Pod, it unable to find the container and cannot mount the given mount path. Ending up giving the below error.

Can someone advise me if I missing any steps or something additional need to be done?

Error:

E1018 09:22:28.758428 9874 nodeserver.go:412] rpc error: code = Internal desc = Mount failed with error: rpc error: code = Unknown desc = exit status 1

Error: failed to initialize new pipeline [failed to authenticate credentials for azstorage] , output:

Please refer to http://aka.ms/blobmounterror for possible causes and solutions for mount errors.

Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
3,183 questions
Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,876 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Sumarigo-MSFT 46,286 Reputation points Microsoft Employee
    2024-10-18T14:27:40.1433333+00:00

    @Gyan Prakash Rai Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

    • Can you please share the screenshot of the error message?
    • Based on your issue you're encountering with mounting the Azure Blob storage using the CSI driver in your Kubernetes deployment. Kindly let me know if I'm incorrect.
    • Make sure you are using the correct access key for the storage account, and it hasn't expired or been regenerated. Verify the credentials that your deployment is using match those for the storage account.
    • Ensure that you are using the appropriate endpoint (blob or dfs) based on the type of file system or blob service you're trying to mount.
    • Sometimes, network issues can cause authentication failures. Verify that your network connection is stable and that there are no firewall rules blocking access to Azure Storage.

    Based on the error message : can you please refer to suggestion mentioned in this link

    Verify the CSI Driver Installation: Make sure that the blob.csi.azure.com storage class driver is correctly installed and configured in your Kubernetes cluster. You can refer to the Azure Blob storage CSI driver documentation for detailed instructions on setting up and troubleshooting the driver.

    Additional information :
    There is a similar thread discussion in SO forum & Microsoft Q&A which gives some idea on your scenario

    If the issue persist after trying the above mentioned suggestion, I would like to work closer on this issue.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.