That would be a great approach! It wouldn't be too difficult for monocular to handle those requests and redirect them accordingly to the right .tgz.

It would probably need to support https://helm.sh/prydonius/wordpress.prov so the --sign flag works with that workflow as well. That would be a really nice transition from the stable charts repo to Helm Hub, though.

Matthew Fisher

Caffeinated Software Engineer

Microsoft Canada

---

From: cncf-helm@... <cncf-helm@...> on behalf of Matt Farina via Lists.Cncf.Io <matt=mattfarina.com@...>
Sent: Thursday, August 1, 2019 12:10 PM
To: Adnan Abdulhussein <aadnan@...>; Czarkowski-Golejewski, Paul (Pivotal) <pczarkowski@...>; cncf-helm@... <cncf-helm@...>
Cc: cncf-helm@... <cncf-helm@...>
Subject: Re: [cncf-helm] PSA: Helm v3 and the Stable repository

 

The timing for this is good. I wonder if Monocular (the software that powers the helm hub) could intercept a call to it based on the client and perform a redirect to the right package file. This could work for Helm v2 as well since `helm install <url to tgz>` works today.

What do y'all think about that?

On Wed, Jul 31, 2019, at 1:16 PM, Adnan Abdulhussein wrote:

Completely agree, I previously brought up the idea of using some sort of vanity URL to make it easier to install charts listed on the Helm Hub (https://github.com/helm/community/pull/24#issuecomment-395235744). For example, allowing users to do `helm install helm.sh/prydonius/wordpress`. The Helm install command could then automatically add the repository and install the chart (similar to how Homebrew works with taps).

On Jul 30, 2019, 2:52 PM -0700, via Lists.Cncf.Io <pczarkowski=pivotal.io@...>, wrote:

While I understand the stated reasons for removing the stable repository, I'm a great believe in decreasing the time to dopamine for using a new tool.  For better or worse being able to run `helm install stable/wordpress` <insert preferred demo project here> is great for a person to get that initial "hey look I did something useful!" feeling.  I have the feeling that any quickstart guide will simple have `helm repo add stable ...` as a second command anyway.

I'm not saying we shouldn't remove it, but I feel like there might be some reduction in the experience for new users that we should make sure we've considered.

On Tue, Jul 30, 2019 at 1:25 PM Matt Farina <matt@...> wrote:

Great question. Two things come to mind.

1) We have a line item to "Remove helm init and support XDG Base Directory" that hasn't happened yet. This should be a fairly straight forward to implement if someone wants to help.

2) I would like to tie the Helm Hub into `helm search` so that anything in there can be discoverable. We still need to deal with alternative search endpoints and just data held locally. I do not want searches to internal systems leaked.  This has not happened either. If someone wants to help with this it would be appreciated.

Does that help?

On Tue, Jul 30, 2019, at 2:18 PM, Fox, Kevin M wrote:

On init, does it at least point folks to the hub.helm.sh site so they can find things easier?

Thanks,

Kevin

---

From: cncf-helm@... [cncf-helm@...] on behalf of Matt Farina [matt@...]
Sent: Tuesday, July 30, 2019 11:07 AM
To: cncf-helm@...
Subject: [cncf-helm] PSA: Helm v3 and the Stable repository

When you initialize Helm it has long added the stable repository. Unless overridden it is set to https://kubernetes-charts.storage.googleapis.com/. Even though Helm is designed to work with numerous distributed repositories this has given the impression or feel of a central repository. The central repository has become more than a handful to manage and scale so it isn't going to work for the next phase of Helm growth.

This is where the Helm Hub comes in. We want to encourage people to host their own charts and share them in a more discoverable place. That is the Helm Hub.

With that in mind, the stable repository has been removed from Helm v3. When you initialize Helm no repository is added by default.