<p dir="auto">Run once pods are not well accounted for by the current quota system, because run-always pods can absorb the quota and prevent jobs from running (builds, scheduled tasks).  We discussed today a "pods per unit time" measure with "max run once pods" that allow for users to run short jobs in parallel or over a longer time.</p>
<p dir="auto">Since run always pods are typically "run up to N pods that run 24 hours a day", it's natural to want to state "run up to 3 pods at most 6 hours a day".  Whether that is 6 hours for one pod or 2 hours for each of 3, the end metric would be applied.  This may be continually refilling (useful).</p>
<p dir="auto">This is, essentially, a deliberate duplicate of <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="170806253" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/30495" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/30495/hovercard" href="https://github.com/kubernetes/kubernetes/issues/30495">#30495</a>, which was closed by the requester before the underlying issue was resolved. In short, current versions of Kubernetes (I'm using 1.3.7) fail when using <code class="notranslate">kube-up.sh</code> to create a cluster under AWS, but incorrectly report success. This leaves some AWS resources (VPCs, security groups, etc.) in place, but with no actual nodes.</p>
<p dir="auto">The relevant bit of output is as follows:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="./cluster/../cluster/../cluster/aws/../../cluster/common.sh: line 528: KUBE_MANIFESTS_TAR_URL: unbound variable
Kubernetes binaries at /Users/jon/kubernetes/cluster/
You may want to add this directory to your PATH in $HOME/.profile
Installation successful!"><pre class="notranslate"><code class="notranslate">./cluster/../cluster/../cluster/aws/../../cluster/common.sh: line 528: KUBE_MANIFESTS_TAR_URL: unbound variable
Kubernetes binaries at /Users/jon/kubernetes/cluster/
You may want to add this directory to your PATH in $HOME/.profile
Installation successful!
</code></pre></div>
<p dir="auto">A viable workaround has been described in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="170806253" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/30495" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/30495/hovercard" href="https://github.com/kubernetes/kubernetes/issues/30495">#30495</a> (I believe this is why the original author closed the issue), but the issue itself has not actually been fixed. Please accept my apologies for the goofy paperwork shenanigans here, but I did want to make sure the issue didn't get lost.</p>