install as host process on windows node and not requiring csi-proxy

[himanshuz2]

Is your feature request related to a problem?/Why is this needed
with hostprocess now available, csi-proxy should not be needed to run this driver on windows nodes

Describe the solution you'd like in detail
a daemonset that can deploy this driver on every windows node on the cluster.

Describe alternatives you've considered
login to every added windows node and install csi-proxy using the methods described
modify the base image for windows node pool to install csi-proxy

Additional context

[andyzhangx]

related to this PR: kubernetes-csi/csi-proxy#179

[himanshuz2]

Found the yaml file to install csi-proxy
https://github.com/kubernetes-sigs/cluster-api-provider-azure/tree/main/templates/addons/windows/csi-proxy

[andyzhangx]

Found the yaml file to install csi-proxy https://github.com/kubernetes-sigs/cluster-api-provider-azure/tree/main/templates/addons/windows/csi-proxy

@himanshuz2 so run following command on k8s 1.23+ cluster would work?

kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-azure/main/templates/addons/windows/csi-proxy/csi-proxy.yaml

[himanshuz2]

Found the yaml file to install csi-proxy https://github.com/kubernetes-sigs/cluster-api-provider-azure/tree/main/templates/addons/windows/csi-proxy

@himanshuz2 so run following command on k8s 1.23+ cluster would work?

kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-azure/main/templates/addons/windows/csi-proxy/csi-proxy.yaml

Yes.

[Termibg22]

Found the yaml file to install csi-proxy https://github.com/kubernetes-sigs/cluster-api-provider-azure/tree/main/templates/addons/windows/csi-proxy

@himanshuz2 so run following command on k8s 1.23+ cluster would work?

kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-azure/main/templates/addons/windows/csi-proxy/csi-proxy.yaml

Yes.

When i try to install it on a RKE2 cluster with 2 windows nodes the pod gives the following error:

I0907 03:07:19.474978 7664 main.go:64] Starting CSI-Proxy Server ... I0907 03:07:19.474978 7664 main.go:65] Version: v1.1.1-0-gc16d19a I0907 03:07:19.474978 7664 main.go:84] Working directories: %v[C:\var\lib\kubelet] 2023-09-07T03:07:19.482378900-07:00 panic: ([]error) 0xc000004c00 2023-09-07T03:07:19.482652900-07:00 2023-09-07T03:07:19.482652900-07:00 goroutine 1 [running]: main.main() 2023-09-07T03:07:19.482652900-07:00 /mnt/vss/_work/1/go/src/github.com/kubernetes-csi/csi-proxy/cmd/csi-proxy/main.go:73 +0x1fd

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten