ACS icon indicating copy to clipboard operation
ACS copied to clipboard

Persistant Volumes in kubernetes

Open tmansson opened this issue 8 years ago • 3 comments

I've been trying to wrap my head around dynamic persistent storage for kubernetes on azure for a long time now, without success.

I see documentation on kubernets.io, in this repo, in blogs but they all seem vague to me and I never get it to work.

The issue might not belong here, since dynamic provisioning seems to be implemented and working. I'm now running against manually created storage blobs, and that is working. But dynamic provisioning just seems so awesome (and necessary in some cases) I want to know what I'm missing.

Is it as easy as it seems, or are there some requirements not covered by these tutorials? Could I spin up a cluster with az acs create and expect it to work, using storageClass for example.

tmansson avatar May 16 '17 12:05 tmansson

One thing that is not mentioned @bialad in most places, first you need to create the stoarge account and then a blob container called 'vhds'. I think I have read some talk about this being done automatically, but for now this needs to be done manually and is not really obvious. Got stock on that for a while as well. Hope it helps.

Globegitter avatar May 23 '17 06:05 Globegitter

Thanks for the answer.

I got it working now by creating a storage account in the same resource group. Is this a requirement? When I used a PersistentVolume to mount from another resource group it worked fine.

If I create a blob container, isn't that public accessible then. Or is it "public" to the resource group?

tmansson avatar Jul 26 '17 08:07 tmansson

@bialad are you using "azure file" storage class? In current version, a storage account must be created in same resource group.

andyzhangx avatar Feb 08 '18 11:02 andyzhangx