cert-manager alpha versions in the helm repo

Created on 1 May 2019 · 9Comments · Source: jetstack/cert-manager

$ helm search jetstack
NAME                    CHART VERSION   APP VERSION     DESCRIPTION
jetstack/cert-manager   v0.8.0-alpha.0  v0.8.0-alpha.0  A Helm chart for cert-manager
jetstack/tor-proxy      0.1.1                           A Helm chart for Kubernetes

The alpha version should be available as the latest, it could break deployments!!!

lifecyclrotten

Source

rimusz

Most helpful comment

there should be an alpha repo, separate from stable

rimusz on 1 May 2019

👍2

All 9 comments

Is there no support in Helm for not selecting suffixed releases? That's a shame, as we'd like to be able to publish alpha/beta versions of the software and make it easy to install.

Is there any way we can 'force' what 'latest' points to?

We do recommend that all users use --version on their Helm install command anyway, so I'd hope that this doesn't break existing deployments.

munnerz on 1 May 2019

Perhaps Helm let's us denote which release is 'latest' in the index.yaml manifest? Selecting solely by timestamp seems quite naive.

munnerz on 1 May 2019

there should be an alpha repo, separate from stable

rimusz on 1 May 2019

👍2

I do always use --version but if somebody is not careful enough might get alpha version installed

rimusz on 1 May 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle stale

retest-bot on 30 Jul 2019

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle rotten
/remove-lifecycle stale

retest-bot on 29 Aug 2019

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

retest-bot on 28 Sep 2019

@retest-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

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/test-infra repository.