[v8.5.0] Create Helm Chart from Static Manifests

[hswong3i]

What type of PR is this?
/kind feature

What this PR does / why we need it:
This PR convert our static deployment manifests from deploy/kubernetes/* into Helm Charts under charts/*, by running a convert script under deploy/util/chart-releaser.sh.

Moreover, it handle the chart release with branch gh-pages, by integrate with https://github.com/helm/chart-releaser-action.

The sample helm repo could find from https://alvistack.github.io/kubernetes-csi-external-snapshotter/index.yaml, by:

helm repo add external-snapshotter https://alvistack.github.io/kubernetes-csi-external-snapshotter
helm repo update
helm search repo external-snapshotter

Before each stable tag release, maintainers only required to:

1. Run the ./deploy/util/chart-releaser.sh and update templates under charts/*/templates/*
2. Double confirm charts/*/values.yml with correct values, e.g. image tags
3. git add --all --force charts/* && git commit

Which issue(s) this PR fixes:
Fixes #551
Fixes #622
Fixes #751

Create Helm Chart from Static Manifests

[k8s-ci-robot]

Hi @hswong3i. Thanks for your PR.

I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[hswong3i]

Sorry @TerryHowe may we continuous the review for #1285 with this new PR?

[k8s-triage-robot]

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

[SkalaNetworks]

I'm sure there's a lot of value in getting this in a Helm Chart

[humblec]

/ok-to-test

[humblec]

cc @xing-yang
Definitely I see this add value to the project

[hswong3i]

Seems like our CI officially failing?

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: hswong3i
Once this PR has been reviewed and has the lgtm label, please assign saad-ali for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[xing-yang]

Sorry, we won't be able to maintain a Helm Chart in the external-snapshotter repo. You can keep this in your own repo.

[hswong3i]

@xing-yang recall the original design of this PR:

This PR convert our static deployment manifests from deploy/kubernetes/* into Helm Charts under charts/*, by running a convert script under deploy/util/chart-releaser.sh.

Moreover, it handle the chart release with branch gh-pages, by integrate with https://github.com/helm/chart-releaser-action.

So this is just the 1st step for Helm support, by manually run the deploy/util/chart-releaser.sh for conversion; the 2nd step could be making this automatically with GitHub Action during stable tag release, therefore no more additional effort (we just need to keep maintenance our EXISTING static deployment manifests).

[k8s-triage-robot]

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle rotten

[k8s-ci-robot]

@hswong3i: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubernetes-csi-external-snapshotter-1-32-on-kubernetes-1-32	34f1036	link	true	/test pull-kubernetes-csi-external-snapshotter-1-32-on-kubernetes-1-32
pull-kubernetes-csi-external-snapshotter-1-34-on-kubernetes-1-34	34f1036	link	false	/test pull-kubernetes-csi-external-snapshotter-1-34-on-kubernetes-1-34
pull-kubernetes-csi-external-snapshotter-1-33-on-kubernetes-1-33	34f1036	link	true	/test pull-kubernetes-csi-external-snapshotter-1-33-on-kubernetes-1-33

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.