Shall we make e.g. library folder and put charts there, as soon we have many charts, this repo will be come unreadable/messy

https://travis-ci.org/helm/charts/builds/112087541#L3103

Looks like we need to specify the namespace for each chart now

Most of the e2e test logic already exists in the helm repo, but we should keep it in the charts repo so that the tests can react to changes within charts.

googling for helm charts this repo comes as a second option from the top.
Craig Box from google asked to rename this repo.

In the Kubernetes documentation they use the following pod definition for being able to manual test services within the cluster with curl/nslookup/etc:

apiVersion: v1
kind: Pod
metadata:
  name: curlpod
spec:
  containers:
  - image: radial/busyboxplus:curl
    command:
      - sleep
      - "3600"
    imagePullPolicy: IfNotPresent
    name: curlcontainer
  restartPolicy: Always

Then you execute:

kubectl exec curlpod -- nslookup nginxsvc

It would be nifty to have this available as a helm chart (would have helped @bacongobbler with testing #25)

We are going to move this and helm to their own org to open up some possibilities for the future of Helm.

We will likely re-se deis/charts to host Deis' own charts, while helm/charts will house generic charts like those we currently have here.

Should be name: alpine

These generally need to be kubectl apply/create'd before the RC manifests. I wasn't sure if helm even supports configmaps yet, but would love to see some examples.

Right now the selenium chart installs the hub as well as the chrome + firefox selenium nodes. Ideally if you're using selenium you'd want to control these or configure these separately, right? It makes sense to me to have a "selenium-hub" chart as well as a "selenium-node" chart. Thoughts @elsonrodriguez?

There are still occasions where this repo shows up at the top of Google search results (e.g. for "cassandra helm").

Would it be worth marking it as not to be archived, by renaming the master branch?

The Docker image referenced in the riak chart is currently broken--see deis/riak#28. This prevents helm chart testing from completing in CI.

We fairly consistently see a situation where a kubectl logs -f [deis-tests] --namespace=deis exits (like it got a connection reset or got an EOF) on ci e2e runs. This makes the test logic think that the tests are done running and therefore kick off the "wait for pod exit code" rigamarole. We should figure out a way to ensure that tests have either finished successfully, still are running, or have errored by adding in a check for pod status (other than container exit code) which can then rekick off a tailing of the test logs.

I'd really love to see a few charts that use the new 1.1 DaemonSet and Job types.

With helm version helm version v0.1.0+c600ce8, I got the following error installing Cassandra:

pentagon:Applications paul$ helm search cassandra
        cassandra (cassandra 0.2.0) - The Apache Cassandra Project.
pentagon:Applications paul$ helm info cassandra
Name: cassandra
Home: http://cassandra.apache.org/
Version: 0.2.0
Description: The Apache Cassandra Project.
Details: This package deploys Cassandra to kubernetes.

pentagon:Applications paul$ helm install cassandra
---> No chart named "cassandra" in your workspace. Fetching now.
---> Running `kubectl create -f` ...
service "cassandra" created
The ReplicationController "cassandra" is invalid.
spec.selector: required value
[ERROR] Failed to upload manifests: exit status 1

There are useful charts... and there are not-so-useful charts. I would like to start the conversation about what makes an awesome chart and create a standard of quality within the deis/charts repo.

One thing that has been discussed thus far:

• all charts need to have service, replication controller, and pod definitions in the chart... unless it doesn't make sense to do so. Deploying a Jenkins master into a kubernetes cluster isn't so useful unless it has all three (rc, pod, service).

I have both 2.2.0 and 2.3.0 charts and am attempting to generate the manifests via:

helmc generate -x -f manifests workflow-v2.3.0

and this results in the following:

[ERROR] Failed to complete generation: lstat /Users/<username>/.helmc/workspace/charts/manifests: no such file or directory

Under the .helmc directory, I have the following dir structure:

~/.helmc/workspace/charts/workflow-v2.2.0
~/.helmc/workspace/charts/workflow-v2.3.0

I'm guessing the error above only case-d in for a single version?