Skip to content

Commit 5fb3cfa

Browse files
authored
Added CSI Proxy Installation steps
1 parent b2a2923 commit 5fb3cfa

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

README.md

+13-1
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,19 @@ CSI drivers are recommended to be deployed as containers. Node plugin containers
66

77
Follow steps [here](./BuildCSIProxy.md) to build the `csi-proxy.exe` binary.
88

9-
After you build the binary you need to place it in every Windows worker node. The easiest way to do this is to install it in the base Windows Server 2019 image and build your stemcell with it. Also make sure you start it as a web service that starts when the machine boots.
9+
## Install CSI Proxy
10+
11+
After you build the binary you need to place it in every Windows worker node. The easiest way to do this in TKGI is to install it in the base Windows Server 2019 image and build your stemcell with it. Add the binary during the stemcell building process, while the VM is powered on before powering it off (before step 8 [here](https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid-Integrated-Edition/1.15/tkgi/GUID-create-vsphere-stemcell.html#remove-hidden-devices-5))
12+
13+
Make sure you start it as a web service that starts when the machine boots. Here's the [upstream documentation](https://github.com/kubernetes-csi/csi-proxy#installation). This is a sample of working steps:
14+
```
15+
# Install the csi-proxy.exe binary in this location: “C:\csi\csi-proxy.exe”
16+
# Then we run these commands
17+
$flags = "-windows-service -log_file=C:\csi\logs\csi-proxy.log -logtostderr=false"
18+
sc.exe create csiproxy start= "auto" binPath= "C:\csi\csi-proxy.exe $flags"
19+
sc.exe failure csiproxy reset= 0 actions= restart/10000
20+
sc.exe start csiproxy
21+
```
1022

1123
## Build CSI Driver
1224
This step should be optional and only needed if certain customization is required in the CSI Driver images.

0 commit comments

Comments
 (0)