-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Create a feature group for Karpenter integration #9523
Comments
/assign @elmiko |
Looking forward to seeing the output of this! /triage accepted |
I'd be interested in helping out with this. |
I'm also interested in this, and watched the previous meeting. |
The time immediately after or before the CAPI working group meeting sounds reasonable to me (would be starting at 9am or 11am PST (UTC−08:00) respectively I believe). Really excited to see what comes out of this collaboration! It definitely seems like there's a good number of areas that Karpenter and CAPI could hope to align on. |
If possible, I'd be interested in helping on this. |
Count me in please :) |
I'd be interested in joining in, mostly to listen (as some of this may be interesting from cluster autoscaler perspective). Though 11am is a bit late in central european tz, so I'm not making any promises if we go with the later slot. |
Excited to be part of this |
thanks for all the great input folks, i will be preparing a PR to create the feature group. i would like to pick a meeting time that will include the most people, but i'm not sure how easy that will be. that said, we will record all meetings and share them on the cluster-api playlist. |
@elmiko thanks for setting this up. I can only commit async time, so can't attend meetings sorry. Would be great for updates to be posted here too. CAPI/Kapenter support is a killer feature |
@ben-wilson-peak thanks, and good suggestion about updates. i will definitely update this issue once the PR for the feature group is posted. as to broadcasting the activities of the feature group, i think we should follow the good practices of the other features groups, meaning:
hopefully that will be sufficient for broadcasting what's happening. we could also post the mailing list after meetings if that would help. |
As discussed during the 27 September 2023 meeting and also in the Cluster API breakout meeting on Karpenter, I am proposing the formation of a feature group to investigate Karpenter integration with Cluster API.
There are several topics of interest that this feature group can answer:
The purpose of this issue is to gather support for the feature group, to identify possible meeting times, and to identify next steps.
As a started for the conversation, other feature groups have used the times immediately before or after the community meeting as their feature group meeting. I wonder if we might consider meeting immediately after the Cluster API community meeting?
The text was updated successfully, but these errors were encountered: