-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Adding ability to configure resources for weave (#8113) #8216
Adding ability to configure resources for weave (#8113) #8216
Conversation
Hi @mmerrill3. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/assign @gambol99 |
8fbbfec
to
b38bafe
Compare
Signed-off-by: mmerrill3 <michael.merrill@vonage.com>
/ok-to-test |
/test pull-kops-e2e-kubernetes-aws |
1 similar comment
/test pull-kops-e2e-kubernetes-aws |
Thanks @mmerrill3! /lgtm Fixes: #8113 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mikesplain, mmerrill3 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 |
@mmerrill3 @mikesplain @rifelpet Any chance this broke the weave plugin? My gu
|
cpu: 50m | ||
memory: 200Mi | ||
cpu: {{ or .Networking.Weave.CPURequest "50m" }} | ||
memory: {{ or .Networking.Weave.MemoryRequest "200mi" }} |
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.
These memory units need to have a capital M
don't they?
https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/#memory-units
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.
That's what I thought also... PR to fix it?
This is a PR to address #8113 whereby kops users can gain the ability to configure resources for the weave and weave-npc containers inside the weave daemonset.
Signed-off-by: mmerrill3 michael.merrill@vonage.com