Hi I need to install Tiller locally for some reasons and the only way to do it is installing from source as I understand. I followerd the steps listed in the docs

We're going to go around sharing it everywhere. I'll try to get to that later today. Thanks for pointing it out. -- Matt Farina mattfarina.com Go in Practice - A book of Recipes for the Go

Matt Thank-you for doing this. Please could you post on some of the CNCF slack channels too? alexis

The survey is available at https://goo.gl/forms/ht61kKETiqVR103v1 Backstory: For the past several months the App Def WG has been looking at how people build applications to run on Kubernetes and tools

Sounds good to me! Michelle Noorali

Thanks Matt Farina! For the how many users question, I think it depends what you want to know. Are you trying to get a sense of how many developers or operators are using helm? Or, is helm the go-to

This looks great! Would it be useful to add an extra section under the "how many users are in your organization" question, asking: Under your current job role, approximately how many users are using

To learn more about what people need out of helm v3 I'm starting to put together a survey. A document with questions is at the following link. If you have any feedback please feel open to adding

As we kick of Helm 3 development, we want to make sure that (a) it is easy to do work on the Helm 3 codebase, and (b) we don't break the Helm experience for existing users. After doing some

Matt Yes, absolutely build is a more complex case. But it can be a super set of packaging, as exemplified by nix. All these systems benefit from being deterministic and compositional, and I think the

Alexis, Thanks for sending that paper out. It was a fun read to start my day. I think it's only tangentially relevant to Helm because Helm is a package manager rather than a build tool. A comparison

Hi Dropping Computer Science, right about now... Ilya dug up this new paper from Simon Peyton-Jones (MS Research) and others. They look at build systems from a theoretical POV. Their objective is

Yup, March 27th works. I've added you to the agenda.. -- Quinton Hoole quinton@...

Hi Matt Thanks, your writeups are very useful. Two comments/questions: 1. Your multi-cluster use cases would be interesting to kubernetes-SIG-multicluster, who might also be able to provide you with

Quinton, I'd be happy to come. Would the March 27th meeting be a good one for this? Good idea. I'll craft a PR. Cheers, Matt -- Matt Farina mattfarina.com Go in Practice - A book of Recipes for the

+1, that is a major usage pattern for us and implemented using flux-helm. I don't think this has implications about what would trigger a pull/upgrade. This is because anything that triggers a pull

Brian, that's a good question. These are definitely similar and may be able to be combined. There have been requests to have a service running in a cluster that watches or is notified of changes in a

Very useful. Questions about 1.1 and 1.8: How are these 2 different? 1.1 is about pulling from cluster-local storage, whereas 1.8 is about pulling from a single source for all clusters? 1.8 is

Dmitry, I can add a little to what Adnan shared... Helm tries to provide a semantic version guarantee to not break APIs on a major version. When the development from Helm v1 to Helm v2, which was

As part of the work to get going on Helm 3, the next major release, we've started to collect a set of user stories. The goal is to collect those that are above and beyond what's currently in Helm 2