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

Adding working group notes #775

Merged
merged 2 commits into from
Oct 28, 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
34 changes: 34 additions & 0 deletions WORKING_GROUP.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,40 @@ Please contribute to our meeting notes by opening a PR.
2. Work Items
3. Demos

# Meeting notes (10/28/21)
## Attendees
- Brandon Wagner
- Suket Sharma
- Michael Mccune
- Felix Huang
- Jason Haugen
- Jerad Cramp
- Ellis Tarn
- Geoffrey Cline
- Alex Kestner
ellistarn marked this conversation as resolved.
Show resolved Hide resolved
- Jacob Gabrielson

## Notes
- Capi Provider work in progress
- Inline Launch Templates
- What about CAPI?
- This corresponds to the machine template
- separate template object
- We can probably wait and do this backwards compatible
- EKS Node Group APIs
- Many users use custom launch templates
- similar problems to have LTs have unnecessary fields (instance type)
- Attribute Based Selection
- Storage
- Supporting persistent volumes
- Tricky because of how we create nodes/bind pods
- WaitForFirstConsumer creates a chicken and egg problem
- Karpenter assigns the pod to the node, but the PV isn't assigned
- Scheduler puts a special label on the PV
- If the PV already exists, we need to launch the pod in that zone
- If multiple volumes are in different zones, it's never going to work
- just need to not make it worse

# Meeting notes (09/30/21)

## Attendees
Expand Down