<p dir="auto">See the log below. A pod (created by a RC) failed to schedule several times. All of the failed attempts are visible along with the one that succeeded. RC's replicas is set to 1.</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="$ kubectl get pods --all-namespaces

NAMESPACE     NAME                                           READY     STATUS                RESTARTS   AGE
[...]
kube-system   monitoring-heapster-v7-1xljv                   1/1       Running               1          1m
kube-system   monitoring-heapster-v7-czp8j                   0/1       InsufficientFreeCPU   0          1m
kube-system   monitoring-heapster-v7-iio5r                   0/1       InsufficientFreeCPU   0          1m
kube-system   monitoring-heapster-v7-r1ddh                   0/1       InsufficientFreeCPU   0          1m"><pre class="notranslate"><code class="notranslate">$ kubectl get pods --all-namespaces

NAMESPACE     NAME                                           READY     STATUS                RESTARTS   AGE
[...]
kube-system   monitoring-heapster-v7-1xljv                   1/1       Running               1          1m
kube-system   monitoring-heapster-v7-czp8j                   0/1       InsufficientFreeCPU   0          1m
kube-system   monitoring-heapster-v7-iio5r                   0/1       InsufficientFreeCPU   0          1m
kube-system   monitoring-heapster-v7-r1ddh                   0/1       InsufficientFreeCPU   0          1m
</code></pre></div>
<p dir="auto">ref: <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="100051594" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/12476" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/12476/hovercard" href="https://github.com/kubernetes/kubernetes/issues/12476">#12476</a></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>.): 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.): kubernetes endpoint namespace unique name collision</p>
<hr>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one): Bug report</p>

<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>):<br>
<code class="notranslate">Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.0", GitCommit:"a16c0a7f71a6f93c7e0f222d961f4675cd97a46b", GitTreeState:"clean", BuildDate:"2016-09-26T18:16:57Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"windows/amd64"}</code></p>
<p dir="auto"><code class="notranslate">Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.0", GitCommit:"a16c0a7f71a6f93c7e0f222d961f4675cd97a46b", GitTreeState:"clean", BuildDate:"1970-01-01T00:00:00Z", GoVersion:"go1.7.1", Compiler:"gc", Platform:"linux/amd64"}</code></p>
<p dir="auto"><code class="notranslate">minikube version: v0.11.0</code></p>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>: minikube</li>
<li><strong>OS</strong> (e.g. from /etc/os-release): windows</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>): minikube</li>
<li><strong>Install tools</strong>: minikube</li>
<li><strong>Others</strong>:</li>
</ul>
<p dir="auto"><strong>What happened</strong>:<br>
Tried to create two endpoints with the same name, in different namespaces. The first endpoint was created successfully within the first namespace. The second endpoint was not created in a second namespace with error <code class="notranslate">Error from server: error when creating "app-2/origin-endpoint.json": endpoints "origin" already exists</code></p>
<p dir="auto"><strong>What you expected to happen</strong>:<br>
The second endpoint should have been created in the second namespace</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):<br>
Follow instructions here: <a href="http://kubernetes.io/docs/user-guide/services/#services-without-selectors" rel="nofollow">http://kubernetes.io/docs/user-guide/services/#services-without-selectors</a></p>
<ol dir="auto">
<li>Create two namespaces</li>
<li>Create first endpoint in first namespace</li>
<li>Create second endpoint in second namespace &lt;- fails due to name collision</li>
</ol>
<p dir="auto"><strong>Anything else do we need to know</strong>:</p>