Publish a Helm repository

[pzduniak]

Now that we have a working Helm chart, let's go ahead and make it usable by setting up a Helm repository. Before this is merged, using the Helm chart is still going to be quite wonky.

My setup replaces the versions of the Helm chart with the value of the Git tag and uses the helm-gh-pages action to regenerate the Helm repository every time there's a new release, which is then exposed through GitHub Pages.

Steps to deploy

1. Merge the PR - this primarily includes a rename of the chart's directory to one matching the "idiomatic" structure of repos that include Helm charts (ie. charts/[pkgname]).
2. Run helm package charts/* in the root of the repository. This should output a file like gubernator-v2.0.0-rc.19.tgz.
3. Move it from the repo, eg. mv gubernator-*.tgz ~.
4. Create a new, empty gh-pages branch - the GitHub Action will push to it.

   git switch --orphan gh-pages

5. Move the file back to the repo's directory, which now should be empty, and generate an index.yaml:

   mv ~/gubernator-*.tgz .
   helm repo index --url https://mailgun.github.io/gubernator/ .

6. Add the files and commit them, pushing the new branch:

   git add .
   git commit -m "initial commit"
   git push -u origin gh-pages

7. Go to https://github.com/mailgun/gubernator/settings/pages and enable GitHub Pages:
   

Afterwards, every new Gubernator release will automatically trigger a new Helm chart version.

Feel free to ping me on Keybase or shoot me an e-mail if you'd like some assistance with the deployment. This is the last change before we can fully migrate to your Helm chart.

[mailgun-ci]

Can one of the admins verify this patch?

[thrawn01]

Thank you for adding this! Could you rebase this branch and I'll get it merged.

[pzduniak]

Rebased :)