azurefile-csi-driver rely on github.com when running on azurelinux

[steigr]

What happened:

Upgrade to 1.33 (1.33.3) requires access to github.com, loads remote code and executes it on the host-os (when running on "azurelinux" ):

https://github.com/kubernetes-sigs/azurefile-csi-driver/blob/master/pkg/azurefile-proxy/install-proxy.sh#L41

What you expected to happen:

CSI-Azurefile should not rely on external services.

How to reproduce it:

• Create private AKS within a vnet which blocks access to external services (particularly github.com).
• Enable storage_profile.file_driver_enabled=true
• csi-azurefile-node crashes in init-phase

Anything else we need to know?:

Related issues:

• Problem updating to 1.33 #2570
• Init Container Fails in v1.33.0 #2571
• [BUG] csi-azurefile broken without access to github.com Azure/AKS#5172

Environment:

• CSI Driver version: v1.33.3
• Kubernetes version (use kubectl version): v1.33.2
• OS (e.g. from /etc/os-release): Microsoft Azure Linux 3.0
• Kernel (e.g. uname -a): 6.6.92.2-1.azl3
• Install tools: n/a
• Others: n/a

[04n0]

In addition to what @steigr is reporting, the install script for AZNFS-mount downloaded from GitHub then tries to download stunnel from www.stunnel.org which is again very suspicious behaviour.

[Sanghamitra-PERSONAL]

We too getting in our env , post Node OS Image upgrade on Azure Linux .

[andyzhangx]

We will disabling aznfs package install in AKS Aug release since aznfs package is already installed by default in AKS vhd image, currently install aznfs on AzureLinux requires access to github.com and www.stunnel.org sites, pls enable it for now, and it would be fixed in AKS Aug release rolling out in next week.

• example logs installing aznfs v0.1.548 on Azure Linux node

+ AZNFS_VERSION=0.1.548
+ echo install aznfs v0.1.548....
+ nsenter --mount=/proc/1/ns/mnt curl -fsSL https://github.com/Azure/AZNFS-mount/releases/download/0.1.548/aznfs_install.sh
+ nsenter --mount=/proc/1/ns/mnt bash
Linux distribution: azurelinux, Arch: x86_64
install aznfs v0.1.548....
^[[0mRetrieving distro info from /etc/os-release...^[[0m
^[[0mUsing 'dnf' instead of 'yum'^[[0m
Last metadata expiration check: 1:42:32 ago on Fri Jul 18 12:18:27 2025.
Package wget-2.1.0-6.azl3.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
Last metadata expiration check: 1:42:35 ago on Fri Jul 18 12:18:27 2025.
Package aznfs_stunnel_custom-0.1.548-1.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!

[Sanghamitra-PERSONAL]

hi @andyzhangx ,
How did you disable aznfs package in AKS ,? as csi secret provider related workloads are managed by Microsoft directly .

[andyzhangx]

hi @andyzhangx , How did you disable aznfs package in AKS ,? as csi secret provider related workloads are managed by Microsoft directly .

@Sanghamitra-PERSONAL we will not disable aznfs package since that package is already installed in latest AKS vhd image, so during azure file driver init, we don't need to install that package again.

[steigr]

Hi Andy,

this is not acceptable (e.g. permitting unverified and untrusted code side-loading and running as root on host-os-level from arbitrary sources).

Sorry :-/

[andyzhangx]

Hi Andy,

this is not acceptable (e.g. permitting unverified and untrusted code side-loading and running as root on host-os-level from arbitrary sources).

Sorry :-/

hi @steigr in next AKS release, we will not install aznfs package inside csi driver, that means it won't trigger that code path. the aznfs package is already installed in latest aks vhd image.

btw, https://github.com/Azure/AZNFS-mount is Microsoft owned repo, that's a trusted source

[rouke-broersma]

@andyzhangx yes however to accept that in outbound firewalls we need to accept the whole of github.com, which opens up all kinds of other sources as well.

[andyzhangx]

@andyzhangx yes however to accept that in outbound firewalls we need to accept the whole of github.com, which opens up all kinds of other sources as well.

@rouke-broersma is it possible to only accept downloading from https://github.com/Azure/AZNFS-mount? this is a temp solution, should be fixed in around end of this month.

[rouke-broersma]

@andyzhangx sure, maybe? But that url doesn't actually serve the content. The content is served by the github cdn and for all I know might not have stable URI's at all. For example this is the URI I got for downloading the install script from the latest release:

https://release-assets.githubusercontent.com/github-production-release-asset/582305699/ce167525-89b5-492a-93f7-6a6c9b5178ed

And this is the URI for the install script in another random release I grabbed:

https://release-assets.githubusercontent.com/github-production-release-asset/582305699/2737b0e2-e211-4e78-8560-d6a095c91e6a

Then you also mentioned allowing stunnel URI's as well. That's a lot of untrusted sources that need to be allowed and for which we can't exactly determine the impact.

[andyzhangx]

@rouke-broersma Install aznfs package by default is a mistake, we will disable it in next week's AKS August release. and if you want to make the change sooner, we have a quick way to disable aznfs package install as long you could provide the aks cluster fqdn, just email me with your aks cluster fqdn or filing an Azure support ticket, thanks.

[rouke-broersma]

We have paused upgrading our clusters so we are fine waiting until next week, but thanks for the offer!

[andyzhangx]

the fix has been rolled out to all public regions now, aznfs package is already installed in aks vhd image, won't be installed during csi driver init container now.

[svonliebenstein]

@andyzhangx According to the AKS release tracker it hasn't been rolled out to all regions yet, or am I looking at the wrong place for this?
https://releases.aks.azure.com/webpage/index.html#tabeuro shows multiple regions still on the v20250720 release version. Or does this already contain the fix?