{"action":"opened","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/26791","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/26791/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/26791/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/26791/events","html_url":"https://github.com/kubernetes/kubernetes/issues/26791","id":158419682,"number":26791,"title":"Unable to use EBS/GCE PV when AWS/GCE host is registered via another cloud provider","user":{"login":"alena1108","id":1562176,"avatar_url":"https://avatars.githubusercontent.com/u/1562176?v=3","gravatar_id":"","url":"https://api.github.com/users/alena1108","html_url":"https://github.com/alena1108","followers_url":"https://api.github.com/users/alena1108/followers","following_url":"https://api.github.com/users/alena1108/following{/other_user}","gists_url":"https://api.github.com/users/alena1108/gists{/gist_id}","starred_url":"https://api.github.com/users/alena1108/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alena1108/subscriptions","organizations_url":"https://api.github.com/users/alena1108/orgs","repos_url":"https://api.github.com/users/alena1108/repos","events_url":"https://api.github.com/users/alena1108/events{/privacy}","received_events_url":"https://api.github.com/users/alena1108/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-06-03T17:51:50Z","updated_at":"2016-06-03T17:51:50Z","closed_at":null,"body":"Kubernetes 1.2.4\r\n\r\nIn Rancher we support Kubernetes as an orchestration framework, while Rancher acts as an infrastructure platform for various cloud providers (DO, AWS, GCE, etc). Rancher is registered as a cloud provider in Kubernetes, and acts as a proxy for other cloud provider's hosts. It was done to enable extra functionality provided by Rancher (overlay network as an example) in addition to functionality given by providers themselves.\r\n\r\nStarting 1.2.4, we were unable to use Kubernetes Persistent volumes feature; the commit below disabled it for us:\r\n\r\n```\r\ncommit c04108e90ca28e341af2bd72bcef6e09e7400763\r\nAuthor: saadali <saadali@google.com>\r\nDate:   Fri Apr 1 16:40:36 2016 -0700\r\n\r\n    Ensure volume GetCloudProvider code uses cloud config\r\n```\r\nIn our case, the provider in the code below is returned as a Rancher provider, not AWS cloud provider, and the error is raised.\r\n\r\n```\r\ncloudProvider := plugin.host.GetCloudProvider()\r\n       awsCloudProvider, ok := cloudProvider.(*aws.AWSCloud)\r\n       if !ok || awsCloudProvider == nil {\r\n               return nil, fmt.Errorf(\"Failed to get AWS Cloud Provider. plugin.host.GetCloudProvider returned %v instead\", cloudProvider)\r\n        }\r\n```\r\n\r\nI wonder what is the recommended approach to unblock Persistent Volumes use for a use case like ours?  "}}
{"actor":{"display_login":"alena1108"}}