-
Notifications
You must be signed in to change notification settings - Fork 93
Description
@andyzhangx Thanks for providing hint of init.sh scripts I was able to successfully mount Azure Blob Storage to GKE nodes running Container-Optimized OS (COS), which are read-only at the root filesystem level.
I wanted to share the approach and ask a follow-up questions.
Context
My use case:
GKE nodes running COS (read-only root filesystem)
Need to mount Azure Blob containers to pods
-
First issue of installation of driver got fixed by the PR#2125 (fix: support blobfuse2 install for GKE cos node #2125)
-
After successfull installation, When using --enable-blobfuse-proxy=true in daemenset I encountered the following error:
E0813 11:50:50.359515 518492 nodeserver.go:459] rpc error: code = Internal desc = Mount failed with error: rpc error: code = Unknown desc = exec: "blobfuse2": executable file not found in $PATH , output:
Although at node level i can see
/home/kubernetes/bin $ echo $PATH
/home/kubernetes/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin
/home/kubernetes/bin $ ls -ltrh |grep blob
-rwxr-xr-x 1 root root 30M Aug 10 15:57 blobfuse2
-rwxr-xr-x 1 root root 39M Aug 10 15:57 blobfuse-proxy
I set the --enable-blobfuse-proxy
flag to false keeping in view discussion in issue #1830 (#1830), and it was able to mount.
Question
What functionality or benefits will I lose by setting --enable-blobfuse-proxy=false instead of keeping it true?
I want to understand the trade-offs so I can decide if I should:
Keep it false in production, or
Try to fix the blobfuse2 not found in $PATH issue and set it back to true.