Merge pull request #514 from andyzhangx/blobfuse-proxy-doc

doc: update blobfuse-proxy doc

Author: andyzhangx

README.md

@@ -43,7 +43,7 @@ This option does not depend on cloud provider config file, supports cross subscr
 ### Install driver on a Kubernetes cluster
  - install via [kubectl](./docs/install-blob-csi-driver.md) on public Azure (please use helm for Azure Stack, RedHat/CentOS)
  - install via [helm charts](./charts) on public Azure, Azure Stack, RedHat/CentOS
-   - configure with [blobfuse-proxy](./pkg/blobfuse-proxy) to make blobfuse mount still available after driver restart
+   - configure with [blobfuse-proxy](./deploy/blobfuse-proxy) to make blobfuse mount still available after driver restart
 
 ### Usage
  - [Basic usage](./deploy/example/e2e_usage.md)

charts/README.md

@@ -4,7 +4,8 @@
  - [install Helm](https://helm.sh/docs/intro/quickstart/#install-helm)
 
 ### Tips
- - configure with [blobfuse-proxy](../pkg/blobfuse-proxy) to make blobfuse mount still available after driver restart
+ - configure with [blobfuse-proxy](../deploy/blobfuse-proxy) to make blobfuse mount still available after driver restart
+   - specify `node.enableBlobfuseProxy=true` together with [blobfuse-proxy](../deploy/blobfuse-proxy)
  - make controller only run on master node: `--set controller.runOnMaster=true`
  - enable `fsGroupPolicy` on a k8s 1.20+ cluster: `--set feature.enableFSGroupPolicy=true`
  - set replica of controller as `1`: `--set controller.replicas=1`

deploy/blobfuse-proxy/README.md

@@ -0,0 +1,20 @@
+# Blobfuse Proxy
+ - supported CSI driver version: v1.1.0 or later version
+ - only available on debian based OS
+
+By default, restart csi-blobfuse-node daemonset would make current blobfuse mounts unavailable. When fuse nodeserver restarts on the node, the fuse daemon also restarts, this results in breaking all connections FUSE daemon is maintaining. You could find more details here: [No easy way how to update CSI driver that uses fuse](https://github.com/kubernetes/kubernetes/issues/70013).
+
+This guide shows how to install a blobfuse proxy on all agent nodes and the proxy would mount volumes, maintain  FUSE connections.
+
+### Step#1. Install blobfuse-proxy on debian based agent nodes
+> following daemonset would also install latest [blobfuse](https://github.com/Azure/azure-storage-fuse) version on the node, set `INSTALL_BLOBFUSE` environment variable as `false` to disable blobfuse installation.
+```console
+kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/blob-csi-driver/master/deploy/blobfuse-proxy/blobfuse-proxy.yaml
+```
+
+### Step#2. Install Blob CSI driver with `node.enableBlobfuseProxy=true` helm chart setting
+> another opition: set `enableBlobfuseProxy=true` in existing `csi-blob-node` daemonset
+```console
+helm repo add blob-csi-driver https://raw.githubusercontent.com/kubernetes-sigs/blob-csi-driver/master/charts
+helm install blob-csi-driver blob-csi-driver/blob-csi-driver --namespace kube-system --version v1.4.0 --set node.enableBlobfuseProxy=true
+```

deploy/csi-blob-node.yaml

@@ -85,6 +85,7 @@ spec:
           args:
             - "--v=5"
             - "--endpoint=$(CSI_ENDPOINT)"
+            - "--enable-blobfuse-proxy=false"
             - "--blobfuse-proxy-endpoint=$(BLOBFUSE_PROXY_ENDPOINT)"
             - "--nodeid=$(KUBE_NODE_NAME)"
             - "--metrics-address=0.0.0.0:29635"

pkg/blobfuse-proxy/README.md

@@ -1,33 +1,5 @@
-# blobfuse-proxy
- - supported CSI driver version: v1.1.0 or later version
- - only available on debian based OS
+# Blobfuse Proxy Development
 
-By default, restart csi-blobfuse-node daemonset would make current blobfuse mounts unavailable. When fuse nodeserver restarts on the node, the fuse daemon also restarts, this results in breaking all connections FUSE daemon is maintaining. You could find more details here: [No easy way how to update CSI driver that uses fuse](https://github.com/kubernetes/kubernetes/issues/70013).
-
-This page shows how to run a blobfuse proxy on all agent nodes and this proxy mounts volumes, maintains FUSE connections. 
-> Blobfuse proxy receives mount request in a GRPC call and then uses this data to mount and returns the output of the blobfuse command.
-
-### Step#1. Install blobfuse-proxy on debian based agent node
-> below daemonset would also install latest [blobfuse](https://github.com/Azure/azure-storage-fuse) version on the node
-```console
-kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/blob-csi-driver/master/deploy/blobfuse-proxy/blobfuse-proxy.yaml
-```
-
-### Step#2. Install Blob CSI driver with `node.enableBlobfuseProxy=true` helm chart setting
-```console
-helm repo add blob-csi-driver https://raw.githubusercontent.com/kubernetes-sigs/blob-csi-driver/master/charts
-helm install blob-csi-driver blob-csi-driver/blob-csi-driver --namespace kube-system --version v1.4.0 --set node.enableBlobfuseProxy=true
-```
-
-#### Troubleshooting
- - Get `blobfuse-proxy` logs on the node
-```console
-kubectl get po -n kube-system -o wide | grep blobfuse-proxy
-csi-blobfuse-proxy-47kpp                    1/1     Running   0          37m
-kubectl logs -n kube-system csi-blobfuse-proxy-47kpp
-```
-
-#### Development
  - install blobfuse-proxy package, run as a service manually
 ```console
 wget https://github.com/kubernetes-sigs/blob-csi-driver/raw/master/deploy/blobfuse-proxy/v0.1.0/blobfuse-proxy-v0.1.0.deb -O /tmp/blobfuse-proxy-v0.1.0.deb