vsphere-csi-driver | vSphere storage Container Storage Interface plugin | Storage library

by kubernetes-sigs Go Version: v3.0.1 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | vsphere-csi-driver Summary

vsphere-csi-driver is a Go library typically used in Storage applications. vsphere-csi-driver has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

vSphere storage Container Storage Interface (CSI) plugin

Support

Quality

Security

License

Reuse

Support

vsphere-csi-driver has a low active ecosystem.

It has 229 star(s) with 163 fork(s). There are 20 watchers for this library.

It had no major release in the last 12 months.

There are 32 open issues and 416 have been closed. On average issues are closed in 193 days. There are 42 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of vsphere-csi-driver is v3.0.1

Quality

vsphere-csi-driver has no bugs reported.

Security

vsphere-csi-driver has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

vsphere-csi-driver is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

vsphere-csi-driver releases are available to install and integrate.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of vsphere-csi-driver

Get all kandi verified functions for this library.

vsphere-csi-driver Key Features

No Key Features are available at this moment for vsphere-csi-driver.

vsphere-csi-driver Examples and Code Snippets

No Code Snippets are available at this moment for vsphere-csi-driver.

Community Discussions

Trending Discussions on vsphere-csi-driver

vsphere-csi-controller fails to start due to "invalid memory address or nil pointer dereference"

QUESTION

vsphere-csi-controller fails to start due to "invalid memory address or nil pointer dereference"

Asked 2020-Mar-31 at 13:56

I am installing k8s and vsphere CPI/CSI following the instructions located here

My setup: 2x centos 7.7 vSphere VM's (50g hd/16g ram), 1 master & 1 node in k8s cluster.

Made it to the part where I create the storageClass (near the end) when I discovered this github issue exactly. OP of the linked issue just started from scratch and their issue went away, so the report was closed. This has not been the case for me as I've redeployed my k8s cluster from scratch a bunch of times now and always hit this wall. Below is the error if you don't want to check the linked github issue.

Anyone have ideas on what I can try to get past this? I've checked my hd and ram and plenty there.

...

ANSWER

Answered 2020-Mar-31 at 13:56

Ok turns out this SIGSEGV was a bug or something and it was caused by a network timeout, making this error kind of a red herring.

Details: My vsphere-csi-controller-0 pod was (and still is actually) unable to reach the vsphere server which caused the container in the pod to timeout and trigger this SIGSEV fault. The CSI contributers updated some libraries and the fault is now gone but the timeout remains. Timeout appears to be my problem and not related to CSI but that's a new question :)

If you want the details of what was fixed in the CSI check the github link in the question.

Source https://stackoverflow.com/questions/59937909

Community Discussions, Code Snippets contain sources that include Stack Exchange Network