-
Notifications
You must be signed in to change notification settings - Fork 777
Description
New repo, staging repo, or migrate existing
Migrate existing
Is it a staging repo?
no
Requested name for new repository
kro
Which Organization should it reside
kubernetes-sigs
Who should have admin access?
a-hilaly, barney-s, bridgetkromhout, cheftako, jlbutler, justinsb, matthchr, nicslatts
Who should have write access?
a-hilaly, barney-s, bridgetkromhout, cheftako, jlbutler, justinsb, matthchr, nicslatts
Who should be listed as approvers in OWNERS?
a-hilaly, barney-s, bridgetkromhout, cheftako, jlbutler, justinsb, matthchr, nicslatts
Who should be listed in SECURITY_CONTACTS?
a-hilaly, barney-s, matthchr
What should the repo description be?
Simplify the creation and management of complex custom resources for Kubernetes.
What SIG and subproject does this fall under?
SIG Cloud Provider
Please provide references to appropriate approval for this new repo
We presented https://docs.google.com/presentation/d/1kiO5s5GQEtuV9RuROh5RkR4Fp80MuqMuz7VC_XdrXEE/edit?usp=sharing at SIG Cloud Provider on August 13, 2025 as documented in https://docs.google.com/document/d/1OZE-ub-v6B8y-GuaWejL-vU_f9jsjBbrim4LtTfxssw/edit?tab=t.0#heading=h.w7i4ksrweimp
SIG Cloud Provider’s charter allows for subprojects (https://github.com/kubernetes/community/blob/master/sig-cloud-provider/CHARTER.md) and specifies that adoption of a subproject happens with tech lead approval as specified in https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md#subprojects (to be confirmed on this issue).
Additional context for request
KRO plans to move https://github.com/kro-run/kro into the kubernetes-sigs organization. Maintainers are ready to coordinate this when kubernetes-sigs maintainers are ready.