{"action":"created","issue":{"url":"https://api.github.com/repos/helm/helm/issues/236","labels_url":"https://api.github.com/repos/helm/helm/issues/236/labels{/name}","comments_url":"https://api.github.com/repos/helm/helm/issues/236/comments","events_url":"https://api.github.com/repos/helm/helm/issues/236/events","html_url":"https://github.com/helm/helm/issues/236","id":117373094,"number":236,"title":"orchestration order when doing helm install","user":{"login":"jchauncey","id":430360,"avatar_url":"https://avatars.githubusercontent.com/u/430360?v=3","gravatar_id":"","url":"https://api.github.com/users/jchauncey","html_url":"https://github.com/jchauncey","followers_url":"https://api.github.com/users/jchauncey/followers","following_url":"https://api.github.com/users/jchauncey/following{/other_user}","gists_url":"https://api.github.com/users/jchauncey/gists{/gist_id}","starred_url":"https://api.github.com/users/jchauncey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jchauncey/subscriptions","organizations_url":"https://api.github.com/users/jchauncey/orgs","repos_url":"https://api.github.com/users/jchauncey/repos","events_url":"https://api.github.com/users/jchauncey/events{/privacy}","received_events_url":"https://api.github.com/users/jchauncey/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-11-17T15:04:48Z","updated_at":"2015-11-17T17:47:12Z","closed_at":null,"body":"So I found a group of manifests for building an elastic search cluster using their best practices. https://github.com/pires/kubernetes-elasticsearch-cluster\r\n\r\nThe problem is you need to running the `kubectl create -f` commands in a particular order for the cluster to get setup correctly. I was wondering how we might do this with helm. \r\n\r\nMy first idea was sort the list of manifests and if you need them run in a particular order you can do \r\n* `1_mymanifest.yaml`\r\n* `2_myothermanifest.yaml`\r\n"},"comment":{"url":"https://api.github.com/repos/helm/helm/issues/comments/157450376","html_url":"https://github.com/helm/helm/issues/236#issuecomment-157450376","issue_url":"https://api.github.com/repos/helm/helm/issues/236","id":157450376,"user":{"login":"technosophos","id":89193,"avatar_url":"https://avatars.githubusercontent.com/u/89193?v=3","gravatar_id":"","url":"https://api.github.com/users/technosophos","html_url":"https://github.com/technosophos","followers_url":"https://api.github.com/users/technosophos/followers","following_url":"https://api.github.com/users/technosophos/following{/other_user}","gists_url":"https://api.github.com/users/technosophos/gists{/gist_id}","starred_url":"https://api.github.com/users/technosophos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/technosophos/subscriptions","organizations_url":"https://api.github.com/users/technosophos/orgs","repos_url":"https://api.github.com/users/technosophos/repos","events_url":"https://api.github.com/users/technosophos/events{/privacy}","received_events_url":"https://api.github.com/users/technosophos/received_events","type":"User","site_admin":false},"created_at":"2015-11-17T17:47:12Z","updated_at":"2015-11-17T17:47:12Z","body":"I agree with @gabrtv. The design of Kubernetes suggests that we shouldn't have to orchestrate things quite this way.\r\n\r\nWhat we did with the `etcd` pod is write a bit of bootstrap code for each piece so that if they came up out of order they could recover. It's also not uncommon to see the sort of Erlang motif that if a service comes up and its environment isn't ready, it should crash and let the supervisor (in this case, Kubelet) handle restarting it.\r\n\r\nhttps://github.com/deis/etcd/blob/master/boot.go#L324"}}