Adopting elmiko/karpenter-provider-cluster-api as a community sub-project

[Michael McCune]

hello Kubernetes SIG Cluster Lifecycle members,

As part of the effort to create a Cluster API provider for Karpenter[0] we have reached the point where the proof-of-concept is minimally viable and the Cluster API community would like to contribute this project to the kubernetes-sigs organization to promote the further growth and experimentation around Karpenter.

The naming and migration of the repo has been discussed with the SIG Autoscaling community on 2024-01-15 [1], and the Karpenter community on 2024-01-18 [2], and most recently in the Cluster API community on 2024-08-07 [3].

We would like to open a discussion about this adoption with the community to hear feedback, concerns, or questions that you might have. Please reach out to me (@elmiko), or the Cluster API maintainers, in the #sig-cluster-lifecycle channel on slack, on the migration pull request[4], or by replying to this email to share your thoughts. We are starting a consensus period for discussion which will culminate in a live discussion at the 20 August SIG Cluster Lifecycle meeting. We have opened a pull request[4] for the repository migration and if there are no pending concerns that need to be address in the discussions here, on the pull request, or at the SIG meeting, we will more forward with the adoption process.

I look forward to your feedback and discussion about this topic.

peace o/

[0] https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/community/20231018-karpenter-integration.md

[1] https://docs.google.com/document/d/1RvhQAEIrVLHbyNnuaT99-6u9ZUMp7BfkPupT2LAZK7w/edit

[2] https://docs.google.com/document/d/18BT0AIMugpNpiSPJNlcAL2rv69yAE6Z06gUVj7v_clg/edit

[3] https://docs.google.com/document/d/1GgFbaYs-H6J5HSQ6a7n4aKpk0nDLE2hgG2NSOM9YIRw/edit#bookmark=id.hoco8dz1s099

[4] https://github.com/kubernetes/org/issues/5097