Deep Debroy

hi, I am not at this point - we ran into some significant challenges with a PoC of this at scale.

hi @npolshakova it looks like at this point this will have to wait till 1.28.

@bswartz the overall flow for this will involve: 1. For NodePublish, SPs calling APIs on a common proxy ([CRuSt](https://github.com/kubernetes/enhancements/pull/2893/files#diff-d29b488a06a8e4aa819829e0634c0affc40f4c4a35fa22738a7d02039ca50128R1081) proxy) to deposit metadata files about the file system operations for...

> rather than the SP talking to CRuSt, couldn't the SP return the relevant info to the CO and then the CO could pass it to CRuSt? Such a model...

Will be handled as part of https://github.com/docker/for-azure/issues/29

The limitations of SMB noted in https://github.com/Azure/azurefile-dockervolumedriver/issues/65 indeed leads to this behavior. Once the Go APIs for attach/detach VHD support for VM Scale Sets is publicly available from Azure, we...

Thanks for pointing this out @jalberto. We will update this shortly and thinking of waiting till the v3 instances become available in all Azure regions. Are you specifically looking to...

Thanks for reporting the issue. We will publish a fix/workaround shortly. @vovimayhem the script is in the `guide` container running in the manager nodes and needs to be patched up.

Yes! @manixx You can now kick off an upgrade to docker to 17.05 (from 17.04) using the following command/container (rather than upgrade.sh earlier) ```docker run -v /var/run/docker.sock:/var/run/docker.sock -v /usr/bin/docker:/usr/bin/docker -ti...

We will be updating the docs with the new mechanism once 17.06 is out.