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

Added working group notes #795

Merged
merged 2 commits into from
Nov 11, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions WORKING_GROUP.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,31 @@ Please contribute to our meeting notes by opening a PR.
2. Work Items
3. Demos

# Meeting notes (11/11/21)

## Attendees
- Jerad Cramp
- Ellis Tarn
- Jason Haugen
- Felix Huang
- Suket Sharma
- Jacob Gabrielson
- Elton Pinto

## Notes
- Limits are great, what about auto repair?
- How do nodes recover from disk/memory pressure? (kubernetes has mechanisms for this: eviction)
- If nodes come online and then become unhealthy later
- Let's address liveness after the limits problem
- What are the dimensions of limits that we want to introduce?
- CPU/GPU/Memory
- What about storage? Should we support all resource requests?
- spec.limits.resources vs spec.maxResources
- This should support folks running separate provisioners per team.
- Helps a cluster admin enforce a limit on each team.
- Setting GPU limits to 0 can help enforce that no GPU instances are launched at all.
- Discussed resource quotas and why that doesn't help us implement limits in this form.
- With quotas you can limit resourceCounts (number of PVs) but not resource properties (say size of a PV)
# Meeting notes (10/28/21)
## Attendees
- Brandon Wagner
Expand Down