Automatically provide pre-release builds after each merge

[AndersBennedsgaard]

Quite a lot has happened since last release. Comparing main with the last commit for release 2.4.0 (/compare/main..5666be) shows "... 110 changed files with 2,004 additions and 10,619 deletions".

This includes several new CRDs, changes to the code-base, documentation, etc. which is not possible to test on anything other than local clusters using K3d or similar, since we do not release snapshots/pre-releases.

Thus, I would like a new v2.5.0 as soon as possible, and we should consider to release more frequently in the future

[swoehrl-mw]

Hi @AndersBennedsgaard. We are already planning a new release for the beginning of December.

More frequent releases would be good, but we currently have a bottleneck in maintainers, so no promises.

[...] which is not possible to test on anything other than local clusters using K3d or similar, since we do not release snapshots/pre-releases.

You can always deploy the current main yourself, it's just a bit of work as you have to build and provide the docker image and deploy the helm chart from git. If you know what you are doing thats a matter of minutes.

[AndersBennedsgaard]

Good to hear that a new release is planned :+1:

You can always deploy the current main yourself, it's just a bit of work as you have to build and provide the docker image and deploy the helm chart from git. If you know what you are doing thats a matter of minutes.

That requires having to build the operator image and push it to an available container registry such that cloud-hosted clusters can access it. Sure it is doable, but not in minutes. And when something like this is annoying to do, you know that many developers won't do it. I'm not saying that you necessarily have to provide a snapshot release of the operator, but I would personally love to have the opportunity to easily test the operator before when new PRs are merged into main.

[swoehrl-mw]

I'm not saying that you necessarily have to provide a snapshot release of the operator, but I would personally love to have the opportunity to easily test the operator before when new PRs are merged into main.

I'll retask this issue as a feature request. We could add an actions workflow that builds and pushes the operator docker image with a dev tag on every merge to main.

[julienkosinski]

This feature could be very nice indeed. In the mean time, if you want, you can use my repo.

Be aware that I may not update this post if I delete it in the future. You should check that https://julienkosinski.github.io/ displays this project README to be sure it still exists.

Add my repo:

helm repo add opensearch-operator https://julienkosinski.github.io

Install the chart with the value manager.image.repository set to ghcr.io/julienkosinski/opensearch-k8s-operator-controller:

helm install opensearch-operator-test opensearch-operator/opensearch-operator --set manager.image.repository=ghcr.io/julienkosinski/opensearch-k8s-operator-controller