{"action":"opened","issue":{"url":"https://api.github.com/repos/kubernetes/helm/issues/1583","repository_url":"https://api.github.com/repos/kubernetes/helm","labels_url":"https://api.github.com/repos/kubernetes/helm/issues/1583/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/helm/issues/1583/comments","events_url":"https://api.github.com/repos/kubernetes/helm/issues/1583/events","html_url":"https://github.com/kubernetes/helm/issues/1583","id":191223105,"number":1583,"title":"should helm assume dynamic PV is setup for a cluster? or should we offer PV help in the CLI?","user":{"login":"jstrachan","id":30140,"avatar_url":"https://avatars.githubusercontent.com/u/30140?v=3","gravatar_id":"","url":"https://api.github.com/users/jstrachan","html_url":"https://github.com/jstrachan","followers_url":"https://api.github.com/users/jstrachan/followers","following_url":"https://api.github.com/users/jstrachan/following{/other_user}","gists_url":"https://api.github.com/users/jstrachan/gists{/gist_id}","starred_url":"https://api.github.com/users/jstrachan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jstrachan/subscriptions","organizations_url":"https://api.github.com/users/jstrachan/orgs","repos_url":"https://api.github.com/users/jstrachan/repos","events_url":"https://api.github.com/users/jstrachan/events{/privacy}","received_events_url":"https://api.github.com/users/jstrachan/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-11-23T09:35:11Z","updated_at":"2016-11-23T09:35:11Z","closed_at":null,"body":"its going to be common for Charts to have `PersistentVolumeClaim` resources. Though the actual `PersistentVolume` will change based on the cluster (e.g. different cloud providers).\r\n\r\nIf a cluster has no dynamic PV enabled; Charts with PVCs won't startup properly - which could lead to odd errors for the user (they may not know much about PV / PVCs). \r\n\r\nI wonder if we need to have some kind of lifecycle in helm that waits to really start the Chart until the PV requirements are met? I guess with cloud native we have to assume anything could go down or not be available at any time; but I wonder if we might want to make suitable PVs being available as a requirement before an app can really be started? (e.g. telling the user the dynamic PV or static PVs that are required to be able to run the app).\r\n\r\nOr at least worse case provide a reasonable UI to help diagnose which apps haven't started due to PV issues etc.\r\n\r\n"}}
{"actor":{"display_login":"jstrachan"}}