-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Update configure-helper.sh to support heapster resource optimizations #66185
Conversation
/assign @gmarek |
In addition to the shell script changes the heapster yaml has been updated to use addon resizer 1.8.3 for the heapster-nanny. Addon resizer 1.8.3 is being used to take advantage of the new minClusterSize flag. Note this is a no-op change. The values specified for heapster-nanny reflect the current configuration used with version 1.8.2.
/ok-to-test |
/retest |
/test pull-kubernetes-e2e-kops-aws |
cluster/gce/gci/configure-helper.sh
Outdated
local -r metrics_cpu_per_node="${HEAPSTER_GCP_CPU_PER_NODE:-0.5}" | ||
local -r eventer_memory_per_node="500" | ||
local -r nanny_memory_per_node="200" | ||
if [[ "${ENABLE_SYSTEM_ADDON_RESOURCE_OPTIMIZATIONS:-}" == "true" ]]; then | ||
# TODO: Set each of the following variables to optimized values. | ||
base_metrics_memory="140Mi" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You probably wanted "${HEAPSTER_GCP_BASE_MEMORY:-140Mi}". I'd drop this 'if' as it's a no-op. It's easy enough to add when you'll have the proper logic figured out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! Thanks. This logic has been implemented to facilitate testing of a complementary change that sets the ENABLE_SYSTEM_ADDON_RESOURCE_OPTIMIZATIONS environment variable.
I've updated this PR with the final scaling policy numbers. So the TODO I had originally added has now been cleaned up. PTAL. Thanks! |
/lgtm |
/assign @yguo0905 |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: piosz, vantuvt, yguo0905 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest
…On Tue., Aug. 14, 2018, 08:13 k8s-ci-robot, ***@***.***> wrote:
@vantuvt <https://github.com/vantuvt>: The following tests *failed*, say
/retest to rerun them all:
Test name Commit Details Rerun command
pull-kubernetes-integration 5d191d8
<5d191d8>
link
<https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/66185/pull-kubernetes-integration/23087/> /test
pull-kubernetes-integration
pull-kubernetes-e2e-kops-aws 5d191d8
<5d191d8>
link
<https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/66185/pull-kubernetes-e2e-kops-aws/101161/> /test
pull-kubernetes-e2e-kops-aws
Full PR test history <https://k8s-gubernator.appspot.com/pr/66185>. Your
PR dashboard <https://k8s-gubernator.appspot.com/pr/vantuvt>. Please help
us cut down on flakes by linking to
<https://git.k8s.io/community/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/kubernetes/kubernetes/issues?q=is:issue+is:open> when
you hit one in your PR.
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://go.k8s.io/bot-commands>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#66185 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ajn6MP1cDbfU3uFnL7ok96m9H28nfiq_ks5uQr77gaJpZM4VPryw>
.
|
/test pull-kubernetes-e2e-kops-aws
…On Tue, Aug 14, 2018 at 10:44 AM k8s-ci-robot ***@***.***> wrote:
@vantuvt <https://github.com/vantuvt>: The following test *failed*, say
/retest to rerun them all:
Test name Commit Details Rerun command
pull-kubernetes-e2e-kops-aws 5d191d8
<5d191d8>
link
<https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/66185/pull-kubernetes-e2e-kops-aws/101194/> /test
pull-kubernetes-e2e-kops-aws
Full PR test history <https://k8s-gubernator.appspot.com/pr/66185>. Your
PR dashboard <https://k8s-gubernator.appspot.com/pr/vantuvt>. Please help
us cut down on flakes by linking to
<https://git.k8s.io/community/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/kubernetes/kubernetes/issues?q=is:issue+is:open> when
you hit one in your PR.
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://go.k8s.io/bot-commands>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#66185 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ajn6MM5aYmlMd4zlhd5k9eRwClrv035Mks5uQuJDgaJpZM4VPryw>
.
|
/test pull-kubernetes-e2e-kops-aws
…On Tue, Aug 14, 2018 at 12:50 PM k8s-ci-robot ***@***.***> wrote:
@vantuvt <https://github.com/vantuvt>: The following test *failed*, say
/retest to rerun them all:
Test name Commit Details Rerun command
pull-kubernetes-e2e-kops-aws 5d191d8
<5d191d8>
link
<https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/66185/pull-kubernetes-e2e-kops-aws/101221/> /test
pull-kubernetes-e2e-kops-aws
Full PR test history <https://k8s-gubernator.appspot.com/pr/66185>. Your
PR dashboard <https://k8s-gubernator.appspot.com/pr/vantuvt>. Please help
us cut down on flakes by linking to
<https://git.k8s.io/community/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/kubernetes/kubernetes/issues?q=is:issue+is:open> when
you hit one in your PR.
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://go.k8s.io/bot-commands>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#66185 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ajn6MAGR2v70zE23FJjedYxxPlvgXbjCks5uQv_AgaJpZM4VPryw>
.
|
/test pull-kubernetes-e2e-kops-aws
…On Tue, Aug 14, 2018 at 2:34 PM k8s-ci-robot ***@***.***> wrote:
@vantuvt <https://github.com/vantuvt>: The following test *failed*, say
/retest to rerun them all:
Test name Commit Details Rerun command
pull-kubernetes-e2e-kops-aws 5d191d8
<5d191d8>
link
<https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/66185/pull-kubernetes-e2e-kops-aws/101241/> /test
pull-kubernetes-e2e-kops-aws
Full PR test history <https://k8s-gubernator.appspot.com/pr/66185>. Your
PR dashboard <https://k8s-gubernator.appspot.com/pr/vantuvt>. Please help
us cut down on flakes by linking to
<https://git.k8s.io/community/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/kubernetes/kubernetes/issues?q=is:issue+is:open> when
you hit one in your PR.
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://go.k8s.io/bot-commands>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#66185 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ajn6MKEAxWNOkJDraFDx5am3tDKE1nM6ks5uQxgjgaJpZM4VPryw>
.
|
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue (batch tested with PRs 66177, 66185, 67136, 67157, 65065). If you want to cherry-pick this change to another branch, please follow the instructions here. |
@vantuvt: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/retest |
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Release note: