<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>):</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Client Version: version.Info{Major:&quot;1&quot;, Minor:&quot;4&quot;, GitVersion:&quot;v1.4.5&quot;, GitCommit:&quot;5a0a696437ad35c133c0c8493f7e9d22b0f9b81b&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2016-10-29T01:38:40Z&quot;, GoVersion:&quot;go1.6.3&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}
Server Version: version.Info{Major:&quot;1&quot;, Minor:&quot;4&quot;, GitVersion:&quot;v1.4.3&quot;, GitCommit:&quot;4957b090e9a4f6a68b4a40375408fdc74a212260&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2016-10-16T06:20:04Z&quot;, GoVersion:&quot;go1.6.3&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}"><pre class="notranslate"><code class="notranslate">Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.5", GitCommit:"5a0a696437ad35c133c0c8493f7e9d22b0f9b81b", GitTreeState:"clean", BuildDate:"2016-10-29T01:38:40Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.3", GitCommit:"4957b090e9a4f6a68b4a40375408fdc74a212260", GitTreeState:"clean", BuildDate:"2016-10-16T06:20:04Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}
</code></pre></div>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>: AWS</li>
<li><strong>OS</strong> (e.g. from /etc/os-release): Ubuntu 14.04.5 LTS</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>): 3.13.0-100-generic</li>
</ul>
<p dir="auto"><strong>What happened</strong>:<br>
We're seeing a slow increase in CPU usage of the controller-manager pod on our<br>
master. When investigating the logs I noticed that after about 60 minutes it<br>
seems to duplicate the replication controller's resync loop (which runs at a<br>
10 minutes interval).</p>
<p dir="auto">Over a period of a day or so this leads to a full resync running about every<br>
second.</p>
<p dir="auto">We're using an ELB in front of the etcd cluster for Kubernetes to talk to.<br>
Turns out we have it configured with a 60 minute idle timeout. Assuming that<br>
this is somehow related I lowered this to 15 minutes, causing it to create even<br>
more resyncs.</p>
<p dir="auto">Talking directly to the etcd servers doesn't seem to have this problem.</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):<br>
Put a loadbalancer between apiserver and etcd that closes idle connections.<br>
I only tested against AWS' ELB.</p>
<p dir="auto"><strong>Anything else do we need to know</strong>:</p>
<ul dir="auto">
<li>
<p dir="auto">Logs for <a href="http://devoo.ps/k8s/c-m.log" rel="nofollow">controller-manager</a>, <a href="http://devoo.ps/k8s/apiserver.log" rel="nofollow">apiserver</a><br>
Run <code class="notranslate">grep -a Observed c-m.log | cut -d ' ' -f 2 | cut -d . -f 1 | uniq -c</code> to get<br>
a short list of resync run timestamps.</p>
</li>
<li>
<p dir="auto">Cluster size is up to 16 nodes, with minimal load on the scheduler</p>
</li>
<li>
<p dir="auto">CPU usage graph for controller-manager: <a target="_blank" rel="noopener noreferrer nofollow" href="https://camo.githubusercontent.com/380595ac25a63d0262caffeb4193fe5ef2584feb70e63a60a427f4026a212d6f/687474703a2f2f6465766f6f2e70732f6b38732f632d6d5f6370752e706e67"><img src="https://camo.githubusercontent.com/380595ac25a63d0262caffeb4193fe5ef2584feb70e63a60a427f4026a212d6f/687474703a2f2f6465766f6f2e70732f6b38732f632d6d5f6370752e706e67" alt="controller-manager cpu usage 7days" data-canonical-src="http://devoo.ps/k8s/c-m_cpu.png" style="max-width: 100%;"></a></p>
</li>
</ul>
<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>.):</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>
<hr>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one):</p>

<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>):</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):</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>:</p>
<p dir="auto"><strong>What you expected to happen</strong>:<br>
The PVC/PV should not be allowed to delete.</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):</p>
<ol dir="auto">
<li>Create a PV and PVC</li>
<li>Create a deployment using the PVC created by 1)</li>
<li>Once the deployment is running, delete the PVC.</li>
<li>Delete PVC succeed.</li>
</ol>
<p dir="auto"><strong>Anything else do we need to know</strong>:</p>