{"action":"closed","issue":{"url":"https://api.github.com/repos/deis/prototype-repo/issues/3","labels_url":"https://api.github.com/repos/deis/prototype-repo/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/deis/prototype-repo/issues/3/comments","events_url":"https://api.github.com/repos/deis/prototype-repo/issues/3/events","html_url":"https://github.com/deis/prototype-repo/issues/3","id":110031727,"number":3,"title":"kubernetes definitions directory","user":{"login":"bacongobbler","id":1360539,"avatar_url":"https://avatars.githubusercontent.com/u/1360539?v=3","gravatar_id":"","url":"https://api.github.com/users/bacongobbler","html_url":"https://github.com/bacongobbler","followers_url":"https://api.github.com/users/bacongobbler/followers","following_url":"https://api.github.com/users/bacongobbler/following{/other_user}","gists_url":"https://api.github.com/users/bacongobbler/gists{/gist_id}","starred_url":"https://api.github.com/users/bacongobbler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bacongobbler/subscriptions","organizations_url":"https://api.github.com/users/bacongobbler/orgs","repos_url":"https://api.github.com/users/bacongobbler/repos","events_url":"https://api.github.com/users/bacongobbler/events{/privacy}","received_events_url":"https://api.github.com/users/bacongobbler/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-10-06T15:16:04Z","updated_at":"2015-12-08T23:17:07Z","closed_at":"2015-12-08T23:17:07Z","body":"In kubernetes there is a way to define all of the required RCs and services in one yaml/json file (as you mentioned in https://github.com/technosophos/prototype-repo/tree/master/def). Perhaps it would be better to leave kubernetes definitions in the root of the project as its own file? Perhaps something like `kube.json`?\r\n\r\nI don't think there's any conventional standard set quite yet in the kubernetes world, so we kinda have the opportunity to create best practices here :)"}}