Heya folks, Ned here again. Azure Files isn't just SMB anymore, we now offer NFS 4.1 as a service! Extreme high availability & durability, full file system semantics, AES-256 encryption at rest, it will do 100K IOPS & 80 Gibps throughput. More info at:
NFS 4.1 support for Azure Files is now in preview
Get started with your first NFS share here.
- Ned "Azure Files isn't just for SMB anymore" Pyle
MicrosoftHello Ned,
Do you have some news about the GA of Azure Files NFS?
Thanks,
BR
Remy
Microsoftevon3 RobotBen Back with answers/suggestions from the Containers team:
1. They don't have a current date to share for NFS client in Windows container support. They definitely encourage you to give them direct, specific feature requests at https://github.com/microsoft/Windows-Containers/issues so they can add it to their roadmap Windows Container Roadmap (github.com)
Some advice: I suggest telling them about how much of your business they are losing here, rather than just stating you want it, like most customers do. Nothing moves a PM's planning more than specific instance count or potential revenue missed, when they are balancing a gigantic pool of requests with a much smaller set of dates and coding resources.
2. I hear you on the SMB container story (I own SMB, as you probably know). Because of how containers work, there are a lot of pieces missing from the usual client capabilities. I don't see any open github requests or roadmap items for symlink support, I definitely suggest filing one. SMB supports symlinks, hardlinks, junction points, reparse points, etc. so this is a specific limitation of the container SMb client; it may have started off intentionally as a security boundary, now is the time to start telling them you need that functionality so we can explore it. Same advice as above.
