-
Notifications
You must be signed in to change notification settings - Fork 820
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
specify resource limits on simple-udp/fleet.yaml #487
specify resource limits on simple-udp/fleet.yaml #487
Conversation
…acked for load testing purposes
Why both requests and limits? i don't think it makes sense to use both? Probably makes life easier to just use a request, so it can burst if need be, but will still give direction to the scheduler. |
Build Succeeded 👏 Build Id: c74477e5-8365-46e6-bef2-a333f0451df5 The following development artifacts have been built, and will exist for the next 30 days:
To install this version:
|
Take a look at: Basically if you specify limit==request, Kubernetes will put the pod in the Guaranteed class and: "Guaranteed pods are considered top-priority and are guaranteed to not be killed until they exceed their limits, or if the system is under memory pressure and there are no lower priority containers that can be evicted." |
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.
LGTM!
Build Succeeded 👏 Build Id: b6421d26-9e6f-48cc-9030-9f653650e754 The following development artifacts have been built, and will exist for the next 30 days:
To install this version:
|
This allows simple-udp to be used for scale testing of GS controller with fewer nodes.