Helm Chart for External Snapshotter

[marcusschiesser]

Is your feature request related to a problem?/Why is this needed
Currently, I have to use my custom-made helm chart. Would be better if there would be an official one.

Describe the solution you'd like in detail
Provide a helm repo with helm chart for external-snapshotter

[jdambly-ns]

I see that there is this chart: https://github.com/piraeusdatastore/helm-charts/tree/main/charts/snapshot-controller

what do people think of pulling this into this repo and make it official. I have no problems helping out, and contributing to helm charts.

[wozniakjan]

what do people think of pulling this into this repo and make it official. I have no problems helping out, and contributing to helm charts.

writing the helm chart is imo less of a problem. Mostly, it will be about low maintenance overhead and ensuring there is no drift between the future chart and kustomize templates in CRD dir + other deployment dirs. The scope here will likely have to include clever tooling ensuring that no future PR introduces inconsistencies between the two deployment methods.

For inspiration, there is something like ^^ in the NFS driver
https://github.com/kubernetes-csi/csi-driver-nfs/blob/v4.2.0/hack/verify-helm-chart.sh

[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

[EHJ-52n]

/remove-lifecycle stale

[tamalsaha]

Hello, an official helm chart in the repo will be much appreciated. Anyone still working on this?

[xing-yang]

See discussions on this PR: #622

You can take a look at the following helm chart. It was updated for v6.3.2.
https://github.com/piraeusdatastore/helm-charts/tree/main/charts/snapshot-controller

[tamalsaha]

Thanks, @xing-yang . I wonder if that pr can be merged. It is open since Dec 1, 2021.

[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

[simon-wessel]

/remove-lifecycle rotten

[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

[frittentheke]

/remove-lifecycle stale

[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

[simon-wessel]

/remove-lifecycle stale