<h2 dir="auto"><strong>What keywords did you search in Kubernetes issues before filing this one?</strong> (If you have found any duplicates, you should instead reply there.):<br>
azure load balancer</h2>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one): Kind of both<br>
<strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>): current master</p>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>: azure</li>
<li><strong>OS</strong> (e.g. from /etc/os-release): CentOS 7.2</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>): Linux ma-k8s-0 3.10.0-327.36.3.el7.x86_64 <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="35192559" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/1" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/1/hovercard" href="https://github.com/kubernetes/kubernetes/issues/1">#1</a> SMP Mon Oct 24 16:09:20 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux</li>
<li><strong>Install tools</strong>: custom Ansible+kubeadm</li>
<li><strong>Others</strong>:</li>
</ul>
<p dir="auto"><strong>What happened</strong>:<br>
The Azure cloud provider complains with "loadbalancer is misconfigured with a different backend pool" when I add custom load balancer rules with separate backend pools through the Azure Portal or through Azure Resource Templates. I need to add these custom rules to expose the Kubernetes API endpoints. Adding a dedicated Azure Load Balancer just for the API is not possible, as otherwise I get error messages about Azure Load Balancer limitations (only one LB allowed per Availability Set)</p>
<p dir="auto"><strong>What you expected to happen</strong>:<br>
I would have expected that the Azure Cloud Provider just ignores existing backend pools.</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):<br>
As described in "What happened"</p>
<p dir="auto"><strong>Anything else do we need to know</strong>:<br>
I created a fix for this and am currently testing this. I will create a PR in a few minutes when everything goes well.</p>
<p dir="auto">I created this issue before finishing the PR because I wanted to discuss the reason behind this limitation?</p>
<p dir="auto"><strong>Is this a request for help?</strong> (If yes, you should use our troubleshooting guide and community support channels, see <a href="http://kubernetes.io/docs/troubleshooting/" rel="nofollow">http://kubernetes.io/docs/troubleshooting/</a>.):<br>
No</p>
<p dir="auto"><strong>What keywords did you search in Kubernetes issues before filing this one?</strong> (If you have found any duplicates, you should instead reply there.):</p>
<p dir="auto">---scheduler extender; node array; NodeList</p>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one):<br>
BUG REPORT</p>

<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>): 1.3.7</p>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>:</li>
<li><strong>OS</strong> (e.g. from /etc/os-release): ubuntu 14.04</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>):</li>
<li><strong>Install tools</strong>:</li>
<li><strong>Others</strong>:</li>
</ul>
<p dir="auto"><strong>What happened</strong>: Scheduler Extender changes to node array nodes []*api.Node, but ExtenderArgs still use NodeList, which will you use in the future.</p>
<p dir="auto"><strong>What you expected to happen</strong>: Use the same parameter</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):</p>
<p dir="auto"><strong>Anything else do we need to know</strong>:</p>