-
Notifications
You must be signed in to change notification settings - Fork 89
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
Docs on how to better allocate resources for each cloud provider #796
Comments
See #792 |
@viniciusdc please do a deep dive into this and try to get a formula for what the resources available are memory/cpu. Also try to test out these numbers with a blank slate gcp and digital ocean kubernetes clusters. That way we know that QHub is not causing the the issues with resources being taken up. Digtal ocean should be easier to work with. I would also just use the gui to spin up/down new instance types. |
You try to use a sample pod e.g. and try to schedule it on these clusters. ...
kind: Pod
spec:
containers:
- name: busybox
image: busybox:latest
resources:
.... You'll have to play with the resources |
This issue has been automatically marked as stale because there was no recent activity in 60 days. Remove the stale label or add a comment, otherwise, this issue will automatically be closed in 7 days if no further activity occurs. |
This issue was closed because it has been stalled for 7 days with no activity. |
@costrouc @viniciusdc - is this still relevant? been a while since there was an update |
Closing in favor of #35 |
In administrative docs FAQ there should be a section/question about how to pick the correct memory/cpu for each cloud provider or in as many as we can find with links to the definitive docs.
The text was updated successfully, but these errors were encountered: