Create helm chart

[DavidNix]

It seems to a popular way to install operators. The fact this is a private repo can be handled by Flux in the same way we need to download the private docker image.

GH Pages seems to be the most popular way for hosting charts.

However, you can also host them on ghcr. GHCR will work the same way as authenticating a private docker image on ghcr.

[DavidNix]

Note, I can't use the GH pages method because they are public by default. You can only get private gh pages if you have an enterprise account.

[DavidNix]

Moving out of Sprint 2. I attempted this and it's going to be more work than the value it will bring. I was able to use the existing kustomize instead.

Also, this was complicated by the fact the operator is still closed source.

Eventually, we will need a helm chart, so I will keep this issue open but de-prioritized.

[morgoved]

i can help to you;)

[DavidNix]

i can help to you;)

Thanks! It seems straight forward with GH pages now that this repo is open source.

[justyntemme]

'helm create operator' will generate a preconfigured helm chart. We will need to do a few things however as the kubernetes configuration requires more interaction between nodes than the default configuration. We will also need to change the image to reflect that of the production tagged docker image for the operator. I will create a branch in my fork and make the changes for review.

EDIT: Generally I would be suggesting a 'deploy' directory with the helm charts living in there, however looking at the GitHub pages we can work from that way no problem. I have a current PR out that will build docker images on pull requests, we can use the 'helm test' strategy with https://github.com/marketplace/actions/helm-chart-testing to get more testing integration coverage on PR's.

One thing to note, is that by using githubs architecture we do make it difficult for someone who may want to fork the helm repo directory within the suggested 'deploy' directory. I am going to research the GitHub suggestion and see if there are any reasons the deploy directory would be better for a platform agnostic approach so other cosmos projects can utilize the work we do here.

EDITEDIT: I have created the PR #224 that will begin the work. Once the chat Is generated I will take it and make the required changes, then reference those custom changes in the releaser stage so that's handled in the generation as well.