{"action":"created","issue":{"url":"https://api.github.com/repos/colemickens/azure-kubernetes-status/issues/11","repository_url":"https://api.github.com/repos/colemickens/azure-kubernetes-status","labels_url":"https://api.github.com/repos/colemickens/azure-kubernetes-status/issues/11/labels{/name}","comments_url":"https://api.github.com/repos/colemickens/azure-kubernetes-status/issues/11/comments","events_url":"https://api.github.com/repos/colemickens/azure-kubernetes-status/issues/11/events","html_url":"https://github.com/colemickens/azure-kubernetes-status/issues/11","id":187039229,"number":11,"title":"Clarify limitations of Azure Load Balancers in Kubernetes in combination with Availabilitty Sets","user":{"login":"codablock","id":1884269,"avatar_url":"https://avatars.githubusercontent.com/u/1884269?v=3","gravatar_id":"","url":"https://api.github.com/users/codablock","html_url":"https://github.com/codablock","followers_url":"https://api.github.com/users/codablock/followers","following_url":"https://api.github.com/users/codablock/following{/other_user}","gists_url":"https://api.github.com/users/codablock/gists{/gist_id}","starred_url":"https://api.github.com/users/codablock/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/codablock/subscriptions","organizations_url":"https://api.github.com/users/codablock/orgs","repos_url":"https://api.github.com/users/codablock/repos","events_url":"https://api.github.com/users/codablock/events{/privacy}","received_events_url":"https://api.github.com/users/codablock/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-11-03T11:52:11Z","updated_at":"2016-11-03T12:14:31Z","closed_at":null,"body":"Today I got two different errors when trying to use the Azure Cloud Provider and a service of type LoadBalancer. Unfortunately I did not make a copy of the log output. Basically the errors told me that there are limitations when using LBs in combination with Availability Sets.\r\n\r\nIn my current deployment, I have 2 Availability Sets. One for the master nodes and one for the minion nodes. If I understand the cloud provider correctly, it tries to add all nodes to the Azure LB and then fails because the nodes are not in the same Availability Sets.\r\n\r\nCan someone clarify the limitations here? Would it be possible to have more control about the behaviour  of the Azure cloud provider? For example, only attach nodes to the LB when they have a desired label set? Or would it be possible that the cloud provider creates one LB per Availability Set?"},"comment":{"url":"https://api.github.com/repos/colemickens/azure-kubernetes-status/issues/comments/258126596","html_url":"https://github.com/colemickens/azure-kubernetes-status/issues/11#issuecomment-258126596","issue_url":"https://api.github.com/repos/colemickens/azure-kubernetes-status/issues/11","id":258126596,"user":{"login":"edevil","id":12426,"avatar_url":"https://avatars.githubusercontent.com/u/12426?v=3","gravatar_id":"","url":"https://api.github.com/users/edevil","html_url":"https://github.com/edevil","followers_url":"https://api.github.com/users/edevil/followers","following_url":"https://api.github.com/users/edevil/following{/other_user}","gists_url":"https://api.github.com/users/edevil/gists{/gist_id}","starred_url":"https://api.github.com/users/edevil/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/edevil/subscriptions","organizations_url":"https://api.github.com/users/edevil/orgs","repos_url":"https://api.github.com/users/edevil/repos","events_url":"https://api.github.com/users/edevil/events{/privacy}","received_events_url":"https://api.github.com/users/edevil/received_events","type":"User","site_admin":false},"created_at":"2016-11-03T12:14:30Z","updated_at":"2016-11-03T12:14:30Z","body":"I also have different availability sets for master and node vms, and it works fine. Only the node vms need to be added to the load-balancer, unless you expose services on the master nodes as well."}}
{"actor":{"display_login":"edevil"}}