-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixing heapster memory requirements. #26109
Conversation
Q-Lee
commented
May 23, 2016
•
edited by zmerlynn
Loading
edited by zmerlynn
@zmerlynn - this fixes the heapster memory usage bug you found |
GCE e2e build/test passed for commit 81ee3e2. |
Thanks for the fix @Q-Lee I'm oncall today so I'm manually merging it to unblock some tests. |
@roberthbailey @Q-Lee @wojtek-t @zmerlynn please fix the breakage to GCI (in cluster/gce/gci/configure-helper.sh). Adding, removing, or renaming a variable in kube-system manifest requires according changes in cluster/gce/gci/configure-helper.sh. Both GCE and GKE CI tests capture the breakage after this PR was merged |
@andyzheng0831 - sorry for the problem. Looking now. |
Fix GCI after #26109 breakage
#26159 should hopefully fix the problem |
Yeah - seems to be fixed now. |
Automatic merge from submit-queue Trusty: fix breakage by #26413 and #26109 The code https://github.com/kubernetes/kubernetes/tree/master/cluster/gce/trusty in both master and release-1.2 branches is broken. Although we already switched to using cluster/gce/gci for 1.3 branch, we will still need to maintain the cluster/gce/trusty code as long as release-1.2 branch is not deprecated. I will make a couple of PR and cherry-picks to make cluster/gce/trusty back to normal. This PR is one of them, which will not be cherry picked to release-1.2. @roberthbailey @dchen1107 @fabioy @zmerlynn cc/ @kubernetes/goog-image