Create a Helm Chart for FaaS

[errm]

A helm chart would make deploying FasS to Kubernetes much simpler, and it is quickly becoming the standard way to try out third party solutions on Kubernetes...

Once FaaS on kubernetes is somewhat stable we can then submit our chart to the official repo ... https://github.com/kubernetes/charts

I am happy to work on this unless someone else wants to give it a go...

[alexellis]

Please go ahead @errm this sounds like a great idea. What repo would it live in?

[errm]

I guess here for now ...

[alexellis]

No problems. Does this also need #3 to be done?

[alexellis]

Hey Ed have you had a go at this?

[svperfecta]

We're actually doing this now. We might be able to get a pull request in for it.

cc: @cforbes

[weikinhuang]

I opened a PR for this, can't use dynamic named services because a few of the containers have hard coded values.

[alexellis]

Thanks for starting this @weikinhuang

@genexp @weikinhuang @errm what do we need to wrap this up? Does it test out OK?

@weikinhuang the hard-coded values are kept in the main FaaS repo here - https://github.com/alexellis/faas/tree/master/prometheus

^ that's where we need to update and then I have to re-push the builds from Docker Hub.

Also - does this create a permanent dependency on helm?

[weikinhuang]

I'll leave it to everyone else on deciding if helm is going to be the preferred deployment method (which lets us get rid of having hard coded values in the main repo, and lets us use configmap mounted volumes). We can also keep the regular yaml files and update them with the configmaps that are found in the helm charts
(thereby removing them from the main repo as well and not having to build custom copies of prometheus and alertmanager).

[alexellis]

I'd say we need to support both for now.. so let's go with the pain. It's easy to remove the hard-coded "vanilla" config in the future if helm is supported on all platforms we need.

Custom copies will be needed for Docker Swarm.

[weikinhuang]

I can create vanilla configmaps for this, would prevent you from having to build 2 images, and we can use stock docker hub images.

[alexellis]

Derek add label: hacktoberfest

[gardlt]

I would be very interested in a openfaas helm chart since i am currently using this for all my deployments. Let me know how I can help.

[alexellis]

Thanks to @weikinhuang for leading this. We still have a few things to do including helm lint:

https://github.com/kubernetes/charts/blob/master/CONTRIBUTING.md#technical-requirements

@genexp, @errm, @gardlt, @e-beach if you can get involved with testing that would be great. I've compiled RBAC instructions here:

https://github.com/openfaas/faas-netes/blob/master/HELM.md

Once we're happy, how do we go about submitting this to the upstream Helm chart repo?

[gardlt]

i cant seem to package the helm chart:
helm packaget ./helm

Error: directory name (helm) and Chart.yaml name (openfaas) must match

[alexellis]

You can use the instructions in the link above for testing.

That error is the result of linting, do a mv helm openfaas and it should sort it.

[alexellis]

Let's find out how to get this chart released and merged in kubernetes/charts

cc/ Captain @Spiddy