[v8.4.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]

[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 xing-yang for approval. For more information see the Code Review Process.

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

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

[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.

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

[TerryHowe]

Added in another PR

[hswong3i]

Added in another PR

Which PR?

[TerryHowe]

I think it is generally preferred to have one change to one PR and this change is not related.

It is like going to the store to buy mangos and you have to take a pound of hamburger with it.

[hswong3i]

Please refer to my original statement:

Before each stable tag release, maintainers only required to:

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

This PR is target to simplify workload for our developers, where the Chart could automatically release with GitHub Action.

Without the changes to deploy/util/chart-releaser.sh, this PR will become half made...