-
Notifications
You must be signed in to change notification settings - Fork 4.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
Etcd memory and cpu requests #6313
Conversation
Hi @integrii. 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. |
@ihoegen 😻 |
/ok-to-test |
/assign ihoegen |
I think you're going to need to add this to
|
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.
Be sure to run make apimachinery && make
locally too, as well as adding the field to v1alpha1 and v1alpha2
I added the config lines to the other cluster config versions, then I hit #6314 when building api machinery. I unset my Once that worked, I get this error:
How do I add said manual conversion? |
See k8s.io/kops/pkg/apis/kops/v1alpha1/zz_generated.conversion.go, there is auto generated comments on those warnings |
I added the stuff generated from the apimachinery run - was that right?? |
lol - did the files that it generates fail the |
Yeah, looks like it's because of some whitespace. Try running |
@ihoegen I gave you access to my branch. Can you run a format on it pretty please? I'm guessing there is a tooling difference that will be annoying to find... |
Gotta fix the Travis CI tests now: https://travis-ci.org/kubernetes/kops/jobs/477460494 Bunch of stuff regarding expected cluster specs |
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
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. |
Whew, okay that was a bit gory. I had to back out a merge from master I did before I could rebase to squash commits because it wanted to rebase everything that had happened to master... We should be down to just one commit from me and two from Ian, to maintain his contributions. I am now going to re-merge master and re-resolve conflicts since the rebase is complete. |
Finally I was able to squash all my contiguous commits between upstream merges. Whoo! |
That looked painful! Thanks for sorting out all the conflicts and squashing the commits :) I've dropped you a message on Slack in regards to the test fix, specifically in the |
@KashifSaadat you're my hero. I made the change - lets see if builds pass! |
/test pull-kops-e2e-kubernetes-aws |
All green! Thanks @integrii 👍 /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ihoegen, integrii, KashifSaadat 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 |
Excellent!! I will try to make time to hit up the Calico specs next. |
Some of our etcd pods end up with etcd memory use that far exceeds the request defaults kops applies. This change adds the ability to specify the pod memory and CPU requests on a per-etcd-cluster basis so that we can up our requests. It also adds a default 200m CPU to etcd clusters named
main
, and 100m otherwise. 100Mi of memory is always assigned by default. This should match prior functionality.Two new options open up for etcd cluster configuration.
cpuRequest
andmemoryRequest
. These, when set, of course override the defaults described here.There are plenty of things I can see that could be improved, like using a constant for the default memory and CPU. I just wasn't sure where to put it. It took me about two days to find all these parts of the code, work around bugs with things like api machinery. Feel free to let me know if something needs refactored or adjusted.
Thanks!