-
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
📖 add proposal for karpenter integration feature group #9571
📖 add proposal for karpenter integration feature group #9571
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
/hold for consensus until EOW as discussed in office hours
LGTM label has been added. Git tree hash: 36c235c93f18482765448d692ca38115a759838b
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm Thx for driving this @elmiko ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/lgtm @elmiko - do you have a meeting invite that you've added people to? |
@richardcase not yet, is there an official calendar where i could set that up? edit: is it worth proposing a change here? https://github.com/kubernetes/community/tree/master/sig-cluster-lifecycle |
lgtm thx @elmiko |
i will make a calendar item to add folks, i'm a little concerned about making it on my red hat calendar account but i will ask around to sig contribex first. /hold cancel |
I think for the community calendar you have to do it with a PR somewhere. @vincepri should know more afaik |
Edit: Nvm, I found the time in the doc changes proposed. |
What this PR does / why we need it:
Adds a proposal for the Karpenter feature group. This will help us to organize the Cluster API community around the activity of Karpenter usage with Cluster API by creating a central point of contact for contributors.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #9523
/area community-meeting