Helm Chart Recommendation about vsphere-csi-driver HOT 17 CLOSED

+1 for this. I see vSphere CPI can be installed using Helm Chart. Very convenient.

from vsphere-csi-driver.

@rhockenbury unfortunately, it isn't. the vSphere driver was rearchitected (and had a significant degree of implementation changes) to take advantage of the new Cloud Native Storage (CNS) functionality. You can read about it here: https://blogs.vmware.com/virtualblocks/2019/08/14/introducing-cloud-native-storage-for-vsphere/

from vsphere-csi-driver.

@mylesagray and @cormachogan have implemented this feature. Helm chart for vSphere CSI driver is available at - https://github.com/cormachogan/vsphere-csi-helmchart/tree/master

from vsphere-csi-driver.

@tirelibirefe I would recommend breaking out these 2 feature requests. It will increase the odds that it gets the correct visibility and priority.

from vsphere-csi-driver.

@tirelibirefe I would recommend breaking out these 2 feature requests. It will increase the odds that it gets the correct visibility and priority.

Sorry; I corrected.

from vsphere-csi-driver.

/assign @shalini-b

from vsphere-csi-driver.

@tirelibirefe How is having a Helm Chart for CSI driver deployment is beneficial? And why the current deployment yamls are not good enough?

from vsphere-csi-driver.

@SandeepPissay
There is nothing wrong with the existing deployment yaml files if you don't miss anything. I just suggested to curtail the deployment procure via Helm Chart.

I spent days to have a working CSI deployment in my 2 different environments because of I missed something in the procedure. If the procedure was shorter, probably I wouldn't miss the detail.

Also; there are some external dependencies (links etc.) in the deployment yaml files; probably they will need to be revised in future. Instead of updating the existing procedure in deployment yaml files, updating/versioning a Helm Chart would help the traceability.

from vsphere-csi-driver.

Deploying via Helm offers many advantages. Helm provides an easy button for deploying an application/set-of-pods through a clean CLI and API. It provides a simple and easy way for end-users to customize basic settings/parameters though that common interface without having to expose all of the knobs and complexities that the YAML provides. On top of describing the deployment as described in @tirelibirefe comment, it also helps end-users from directly modifying YAML and making mistakes.

You can find the chart for the CPI here: https://github.com/helm/charts/tree/master/stable/vsphere-cpi

from vsphere-csi-driver.

+1 for an official helm chart.

@dvonthenen - Is your previous work still useful? helm/charts#10408

from vsphere-csi-driver.

@dvonthenen thank you for your work, is there a helm chart for vsphere-csi still work? it can help me install quickly

from vsphere-csi-driver.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from vsphere-csi-driver.

/remove-lifecycle stale

from vsphere-csi-driver.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from vsphere-csi-driver.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

from vsphere-csi-driver.

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

from vsphere-csi-driver.

@fejta-bot: Closing this issue.

from vsphere-csi-driver.