REQUEST: Create kubernetes-sigs/cluster-autoscaler repository #6221
Description
New repo, staging repo, or migrate existing
migrate part of existing repo
Is it a staging repo?
no
Requested name for new repository
cluster-autoscaler
Which Organization should it reside
kubernetes-sigs
Who should have admin access?
https://github.com/orgs/kubernetes/teams/autoscaler-admins
Who should have write access?
https://github.com/orgs/kubernetes/teams/autoscaler-admins
Who should be listed as approvers in OWNERS?
https://github.com/orgs/kubernetes/teams/autoscaler-admins
Who should be listed in SECURITY_CONTACTS?
https://github.com/orgs/kubernetes/teams/autoscaler-admins
What should the repo description be?
Provider-agnostic core logic for Kubernetes Cluster Autoscaler, including the cluster snapshot, scale-up/down decision logic, and external/test provider interfaces.
What SIG and subproject does this fall under?
SIG Autoscaling
Please provide references to appropriate approval for this new repo
Additional context for request
This project follows the architectural pattern of karpenter and cluster-api, moving toward a "Core + Provider" model. The goal is to seed this repo with code from the existing autoscaler, retaining only kubemark, kwok, mock, and externalgrpc providers within the core.
Checklist:
- I have reached out to the SIG and received approval to create this repository.
- The repository will contain an OWNERS file.
- The repository will be licensed under Apache License 2.0.
- I am aware that I need to add a README.md and CONTRIBUTING.md.