Skip to content

Commit 5430298

Browse files
authored
Merge pull request kubernetes-sigs#9571 from elmiko/add-karpenter-integration-feature-group
📖 add proposal for karpenter integration feature group
2 parents 0eb51f0 + 5cc250b commit 5430298

File tree

1 file changed

+76
-0
lines changed

1 file changed

+76
-0
lines changed
Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
---
2+
title: Feature Group for Integrating Karpenter with Cluster API
3+
authors:
4+
- "@elmiko"
5+
reviewers:
6+
- "@mtougeron"
7+
- "@cnmcavoy"
8+
- "@nishant221"
9+
- "@faermanj"
10+
- "@ben-wilson-peak"
11+
creation-date: 2023-10-18
12+
last-updated: 2023-10-18
13+
status: proposed
14+
see-also:
15+
- https://github.com/kubernetes-sigs/cluster-api/issues/9523
16+
- https://www.youtube.com/watch?v=t1Uo18v8g48
17+
- https://karpenter.sh
18+
---
19+
20+
# Karpenter Integration with Cluster API
21+
22+
This document briefly outlines the scope, communication media, and
23+
stakeholders for a formal Feature Group dedicated to exploring and
24+
defining how Karpenter can be integrated with Cluster API.
25+
26+
## User Story and Problem Statement
27+
28+
As a Cluster API administrator who uses node autoscaling to manage resource
29+
in my clusters, I would like to utilize the Karpenter project with Cluster API
30+
so that I can gain access to its features and capabilities.
31+
32+
At the time of writing, the Cluster API project only officially supports the
33+
Kubernetes Cluster Autoscaler (CAS)for automatically managing node resources.
34+
The Karpenter project is an alternative node autoscaler and autoprovisioner
35+
which has community requested features, such as pod consolidation, that do not
36+
have equivalents in the CAS. We would like to determine how Cluster API users
37+
can utilize Karpenter, and if necessary create community supported projects to
38+
support this activity.
39+
40+
## Scope
41+
42+
The scope of this effort will be the following:
43+
44+
1. Determine what options are available for a consistent Karpenter on Cluster
45+
API experience.
46+
2. Agree upon a path forward to guide the Cluster API community with Karpenter
47+
usage.
48+
49+
Depending on the outcome of the 2nd item above, we may choose to keep this
50+
Feature Group active during the longer term to support Karpenter integration
51+
design and work efforts in Cluster API, with the blessing of the larger
52+
Cluster API community.
53+
54+
## Communication
55+
56+
We will meet on [Wednesdays at 11:00 PT (Pacific Time)][zoomMeeting].
57+
[Convert to your timezone][convert]. Meeting notes will be documented in this
58+
[HackMD document][agenda]. Meetings will be recorded and posted to the
59+
[SIG Cluster Lifecycle YouTube playlist][playlist].
60+
61+
Regular, summarized updates of group progress will be provided during weekly
62+
Cluster API office hours on Wednesdays @ 10:00 PT on [Zoom][zoomMeeting].
63+
64+
Chat with stakeholders on Kubernetes [Slack](http://slack.k8s.io/) in the
65+
[cluster-api](https://kubernetes.slack.com/archives/C8TSNPY4T) channel.
66+
67+
## Stakeholders
68+
69+
Primary Stakeholders are listed below:
70+
71+
- Michael McCune (@elmiko, Red Hat)
72+
73+
[zoomMeeting]: https://zoom.us/j/861487554
74+
[convert]: http://www.thetimezoneconverter.com/?t=11:00&tz=PT%20%28Pacific%20Time%29
75+
[agenda]: https://hackmd.io/@elmiko/ryR2VXR0n
76+
[playlist]: https://www.youtube.com/playlist?list=PL69nYSiGNLP29D0nYgAGWt1ZFqS9Z7lw4

0 commit comments

Comments
 (0)