+1

+1 !

+1 !

Yes, +1

Hello, thanks for sharing. I took a look at the source. Maybe you can explain the project a bit more- is the purpose of this so that you can see your charts listed in "helm chart list" upon upload via

I might also recommend bypassing your remote Tiller entirely to reduce a lot of ops headache. I've been using the helm-tiller plugin which starts a Tiller server locally for the lifetime of your comma

Just so everyone has reference, Steve is referring to the fact that the "chart" and "registry" subcommands in Helm 3 are hidden behind an experimental env var. For more info, please see this doc: http

The feature gates approach sounds good to me. In general, I’m in favor of keeping the work in tree and marking experimental (vs. plugin). @Matt when/where would the feature gates be configured? On “he

Sure - I think what I'm getting at is on the client side we may need to determine whether the ref in question is a traditional .tgz or if hosted on a registry. Requesting a chart from registry is not

This is all great - just want to keep in mind how this will work alongside registry-based charts, where URL is always the ref being used. Perhaps we have a HEAD/GET request to check to see if the url

Hi all, please see this new repo started as the home for Helm acceptance testing: https://github.com/helm/acceptance-testing This is a test suite built using the Robot Framework, with Python libraries

Mentioned in my message above is "helm search" work for Helm 3.. Out of curiosity, does anyone normally use the "helm search" command to search for charts? I usually obtain the chart string ahead of t

I'm going ahead and cancelling the weekly repos call. We have had initial set of changes related to this merged last week, and we can continue to iterate from there. If we have additional things to di

Over the past several months, we have been working on putting together some changes that would allow users to store their Helm charts in container registries. The level of collaboration has been prett

In a typical ChartMuseum installation, uploads are protected by a single basic auth username/password combo. In this scenario, anyone with this credential pair can upload chart packages to the wrong t

ChartMuseum v0.8.0 has been released! You can check out the release notes here: https://github.com/helm/chartmuseum/releases/tag/v0.8.0 ..and of course with this release also comes a brand new logo an

Here is the proposed change related to --version flag: https://github.com/helm/community/pull/65 feedback welcome!

It was asked in dev call today if there will be a time for everyone to meetup. Guessing there probably will not be an "official" gathering due to conflicting schedules etc, but here are some chances f

Stef- More or less, yes. It is the goal of the change. This is coming from desire to align Helm with the user experience of "docker pull", "docker push".

Thanks everyone for joining today. I think we are making some progress. Here are the notes: https://hackmd.io/6cEbLF6DQlyGtUbsJAKQzg?view What was decided today (please shout if you disagree!) Keep he