Skip to content
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

Allow users to set memory/cpu reservation and limits #12

Closed
scothis opened this issue Jun 19, 2019 · 1 comment
Closed

Allow users to set memory/cpu reservation and limits #12

scothis opened this issue Jun 19, 2019 · 1 comment
Labels
Projects

Comments

@scothis
Copy link
Contributor

scothis commented Jun 19, 2019

Pods can reserve cpu, memory and other resources in addition to setting a maximum limit for those resources. When scheduling the build pod, the pod is guaranteed access to the reserved resource limit and may consume up to the limit. If the cluster does not have the reservation available, the pod will not start until the cluster has capacity. Many clusters will run with the LimitRanger API Server extension that will default these limits. Builds that need addition capacity will need to specify higher limits.

The Image and Build resources should allow a user to specify these values, or at least support t-shirt sizes.

@matthewmcnew
Copy link
Collaborator

This should be available for all non Knative containers in: #37.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Development

No branches or pull requests

2 participants