ADD local host connection minio

[jinjianming]

"Hello @vitalif, I've found that when MinIO and CSI are in the same cluster, and there's no external domain name, using systemd's GeeseFS prevents the connection through Kubernetes' service-ClusterIP. In the case of using systemd, a connection to the NodePort of the MinIO-service is mandatory.

Based on the above description, I've made some code modifications. I would appreciate it if you could review them."

[jinjianming]

I0429 03:53:16.018665       1 geesefs.go:158] Starting geesefs using systemd: /data/lib/rancher/k3s/kubelet/plugins/ru.yandex.s3.csi/geesefs -f -o allow_other --endpoint http://csi-minio.xiaopiu.svc:9000 --setuid 65534 --setgid 65534 --memory-limit 1000 --dir-mode 0777 --file-mode 0666 jsdesign: /data/lib/rancher/k3s/kubelet/plugins/kubernetes.io/csi/pv/nc-ossroot-pv/globalmount
E0429 03:53:48.708703       1 utils.go:101] GRPC error: Timeout waiting for mount

[jinjianming]

New feature self-test log

I0429 05:31:35.210339       1 driver.go:73] Driver: ru.yandex.s3.csi 
I0429 05:31:35.210431       1 driver.go:74] Version: v1.34.7 
I0429 05:31:35.210443       1 driver.go:81] Enabling controller service capability: CREATE_DELETE_VOLUME
I0429 05:31:35.210452       1 driver.go:93] Enabling volume access mode: MULTI_NODE_MULTI_WRITER
I0429 05:31:35.210759       1 server.go:108] Listening for connections on address: &net.UnixAddr{Name:"//csi/csi.sock", Net:"unix"}
I0429 05:31:36.043244       1 utils.go:97] GRPC call: /csi.v1.Identity/GetPluginInfo
I0429 05:31:37.963170       1 utils.go:97] GRPC call: /csi.v1.Node/NodeGetInfo
I0429 05:32:31.407846       1 utils.go:97] GRPC call: /csi.v1.Node/NodeGetCapabilities
I0429 05:32:31.416532       1 utils.go:97] GRPC call: /csi.v1.Node/NodeStageVolume
I0429 05:32:31.421883       1 geesefs.go:154] minio url: http://172.16.10.110:30080
I0429 05:32:31.421906       1 geesefs.go:158] Starting geesefs using systemd: /data/lib/rancher/k3s/kubelet/plugins/ru.yandex.s3.csi/geesefs -f -o allow_other --endpoint http://172.16.10.110:30080 --setuid 65534 --setgid 65534 --memory-limit 1000 --dir-mode 0777 --file-mode 0666 jsdesign: /data/lib/rancher/k3s/kubelet/plugins/kubernetes.io/csi/pv/nc-ossroot-pv/globalmount
I0429 05:32:31.468853       1 utils.go:97] GRPC call: /csi.v1.Node/NodeGetCapabilities
I0429 05:32:31.473370       1 utils.go:97] GRPC call: /csi.v1.Node/NodePublishVolume
I0429 05:32:31.473588       1 nodeserver.go:121] target /data/lib/rancher/k3s/kubelet/pods/d6ba9192-2aa5-4aa7-8f00-c8ff4562d492/volumes/kubernetes.io~csi/nc-ossroot-pv/mount
readonly false
volumeId jsdesign
attributes map[capacity:512Gi csi.storage.k8s.io/ephemeral:false csi.storage.k8s.io/pod.name:js-design-import-55rxs csi.storage.k8s.io/pod.namespace:default csi.storage.k8s.io/pod.uid:d6ba9192-2aa5-4aa7-8f00-c8ff4562d492 csi.storage.k8s.io/serviceAccount.name:default mounter:geesefs options:--memory-limit 1000 --dir-mode 0777 --file-mode 0666]

[mmraz]

Do you have the minio service configured to forward and load balancer to your pods? This should expose the service which other pods can use. The instructions are in the production setup documentation and not included in the minio-dev setup which uses port forwarding to the pod to connect to the api. Try https://min.io/docs/minio/kubernetes/upstream/operations/install-deploy-manage/deploy-minio-tenant.html#connect-to-the-tenant