REQUEST: Migrate elmiko/karpenter-provider-cluster-api

[elmiko]

New repo, staging repo, or migrate existing

migrate existing elmiko/karpenter-provider-cluster-api

Is it a staging repo?

no

Requested name for new repository

karpenter-provider-cluster-api

Which Organization should it reside

kubernetes-sigs

Who should have admin access?

elmiko, fabriziopandini, sbueringer, vincepri

Who should have write access?

elmiko, mtulio, vrabbi, mtougeron, chrischdi, enxebre, fabriziopandini, killianmuldoon, sbueringer, vincepri

Who should be listed as approvers in OWNERS?

elmiko, mtulio, vrabbi, mtougeron, chrischdi, enxebre, fabriziopandini, killianmuldoon, sbueringer, vincepri

Who should be listed in SECURITY_CONTACTS?

elmiko, fabriziopandini, vincepri

What should the repo description be?

Cluster API Karpenter provider. Karpenter is a Kubernetes Node Autoscaler built for flexibility, performance, and simplicity.

What SIG and subproject does this fall under?

sig cluster-lifecycle, sub-project cluster-api

Please provide references to appropriate approval for this new repo

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

Additional context for request

This topic will also be discussed after a consensus period on 20 August at the next SIG Cluster Lifecycle meeting.

[elmiko]

/sig cluster-lifecycle

[elmiko]

happy for comments on this PR, but we don't want to merge this until after the SIG cluster lifecycle meeting on 20 August 2024.

/hold until 2024-08-20

[vincepri]

+1

[chrischdi]

+1

[neolit123]

+1

[neolit123]

github team, we discussed that we need consensus from the sig leads before the migration.
waiting on @fabriziopandini and @justinsb

[vincepri]

Nit: new name could/should be in line with other providers like cluster-api-provider-karpenter

[elmiko]

@vincepri since this is a provider for karpenter i was continuing the naming scheme that aws and azure had established: https://github.com/aws/karpenter-provider-aws, https://github.com/azure/karpenter-provider-azure

just to be clear, the repo in question here does not create cluster-api controllers, it makes a karpenter binary.

[fabriziopandini]

I'm +1 to host the project in this incubation phase.
Considering the topic, It would be great to have some +1 also from SIG autoscaling and karpenter working group folks
Similarly, it would be well accepted to see other folks who participated to the initial design phase to step up as a maintainer (possibily from a mix of companies too)

[elmiko]

Considering the topic, It would be great to have some +1 also from SIG autoscaling and karpenter working group folks Similarly, it would be well accepted to see other folks who participated to the initial design phase to step up as a maintainer (possibily from a mix of companies too)

agreed, i think that would be great.

cc @jonathan-innis @ellistarn @gjtempleton @MaciekPytel to cover karpenter and sig autoscaling people

for the other maintainers, perhaps we should have a discussion at a cluster-api office hours? (i can think of a few people who would be good candidates)

[elmiko]

just a quick update, i am planning to attend upcoming sig autoscaling and karpenter wg meetings, and also reach out to a few people directly about maintainership. happy to also have a conversation at an upcoming cluster api meeting.

[MaciekPytel]

+1
@gjtempleton Unless you have some objections from sig-autoscaling side?

Also - I agree with comments above, we should have someone from karpenter side +1 as well.

[elmiko]

i've added Marco Braga (@mtulio) as another owner, he is a colleague at Red Hat who has been following and participating in the initial design work around karpenter capi, and he also has some experience operating karpenter for aws.