Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Enhancement] Publish release candidate versions on helm repo

See original GitHub issue

Strimzi helm repo contains only stable release versions. Installing release candidates versions of Strimzi directly from helm will be handy for early adopters.

Helm already segregates between stable and development versions based on SemVer postfix presence on install/search/upgrade commands. So publishing release candidate versions will be harmless to actual repo users.

$ helm install --help

This command installs a chart archive.
...
      --devel                        use development versions, too. Equivalent to version '>0.0.0-0'. If --version is set, this is ignored
...

I’ve notice that pre-release helm chart tgz already is published on GitHub, so it seems that is just a matter of re-indexing repo.

After this change, we could

$ helm search repo strimzi 
NAME                            CHART VERSION   APP VERSION     DESCRIPTION                                
strimzi/strimzi-kafka-operator  0.18.0          0.18.0          Strimzi: Apache Kafka running on Kubernetes
$ helm search repo strimzi --devel 
NAME                            CHART VERSION   APP VERSION     DESCRIPTION                                
strimzi/strimzi-kafka-operator  0.19.0-rc1      0.19.0-rc1      Strimzi: Apache Kafka running on Kubernetes
$ helm install strimzi/strimzi-kafka-operator --devel  # installs last release candidate operator version

Is this feature desirable/feasible/PRs acceptable?

PS: I’ve noticed that helm index on pre-release versions already are up to date, and adding this as a helm repo allows using pre-release versions. It’s trickier than using an unified repo, but do the work.

Issue Analytics

State:
Created 3 years ago
Comments:8 (6 by maintainers)

Top GitHub Comments

1reaction

scholzjcommented, Jul 25, 2020

Hmm, nice. I didn’t know about this feature. I opened strimzi/strimzi.github.io#174 to give it a try. The preview should be available here if you wanna give it a try and let me know if this works: https://deploy-preview-174--strimzi.netlify.app/charts/index.yaml

0reactions

scholzjcommented, Mar 31, 2022

Triaged on 31.3.2022: There is no actual code change to be done as part of this. It is just a manual process which would change. Currently, the Helm Charts for RCs are published to the GitHub releases and can be used from there.

Top Results From Across the Web

Release Checklist - Helm

Checklist for maintainers when releasing the next version of Helm. ... Write the Release Notes; PGP Sign the downloads; Publish Release; Update Docs ......

Provide Release Notes file, or remove alpha/beta ... - GitHub

Describe the solution you'd like A Release Notes file, or no duplicate notes in the Releases tab due to internal alpha/beta versio...

Release Procedure - Apache YuniKorn

Release candidates should be tagged with the version and build number of the release ... helm chart files (yunikorn-release repository only); click Publish...

Deploying apps on multiple Kubernetes clusters with Helm

Note: By the time you'll read this blog post Helm 3's first release candidate will have already been announced. This major version is...

HELM Best practices · Codefresh | Docs

First, you package and push the Helm chart in a repository and then you deploy it to your cluster. This way your Helm...