REQUEST: Migrate everettraven/crd-diff to kubernetes-sigs/crdify

[everettraven]

New repo, staging repo, or migrate existing

https://github.com/everettraven/crd-diff

Is it a staging repo?

no

Requested name for new repository

crdify

Which Organization should it reside

kubernetes-sigs

Who should have admin access?

everettraven, JoelSpeed, jpbetz

Who should have write access?

everettraven, JoelSpeed, jpbetz

Who should be listed as approvers in OWNERS?

everettraven, JoelSpeed, jpbetz

Who should be listed in SECURITY_CONTACTS?

everettraven, JoelSpeed, jpbetz

What should the repo description be?

crdify is a CLI tool for comparing the OpenAPI schema of CustomResourceDefinitions to identify incompatible changes. It checks for common mistakes and enforces best practices for maintaining CustomResourceDefinitions. The compatibility checks implemented by crdify are based on the Kubernetes API Conventions.

What SIG and subproject does this fall under?

sig-api-machinery

Please provide references to appropriate approval for this new repo

Relevant KEP: kubernetes/enhancements#5102
Discussed previously at 11th December 2024 SIG API Machinery meeting
Discussed with @jpbetz and @deads2k in slack for migration: https://kubernetes.slack.com/archives/C08MNH7PH9P/p1746207325430499

Additional context for request

All current contributors are Kubernetes org, or Kubernetes Sigs org members, or have previously contributed to the CNCF and therefore have signed the appropriate CLA.

[jpbetz]

/approve
For API Machinery

We discussed and approved this in the KEP and on slack.

Thanks!

[deads2k]

/lgtm

from me as well.

[Priyankasaggu11929]

/assign

@everettraven – could you please address the following items (per kubernetes-repositories.md#rules-for-donated-repositories) before we initiate the migration process:

• Repo should contain template files as per the kubernetes-template-project.

• Please add the standard Kubernetes header to code files (this can can occur post-transfer, but should ideally occur shortly thereafter).

• [Blocking] We need to ensure that all existing committers to the code of crd-diff repo have signed the CNCF CLA

  • @griffindvs – could you please confirm if you have already signed the CNCF CLA?
    If not, could you please do so before we can proceed with the migration. Thanks!
    If you have concerns with signing the CLA and you do not wish to, we'll need to add a NOTICE file to the repo to document your contributions (example).

@everettraven – I will send you an invite to an intermediary org to transfer the repo to Kubernetes project, once above item are addressed. Thank you!

[griffindvs]

Hi @Priyankasaggu11929 , yes, I've signed the CNCF CLA as a corporate contributor under IBM. My CLA coverage can be seen in this PR: kubernetes-sigs/controller-runtime#2875

[Priyankasaggu11929]

Hi @Priyankasaggu11929 , yes, I've signed the CNCF CLA as a corporate contributor under IBM. My CLA coverage can be seen in this PR: kubernetes-sigs/controller-runtime#2875

Thank you for confirming, @griffindvs

---

@everettraven – now the following items are pending, before we begin the migration:

• Repo should contain template files as per the kubernetes-template-project.

• Please add the standard Kubernetes header to code files (this can can occur post-transfer, but should ideally occur shortly thereafter).

[everettraven]

Thanks @Priyankasaggu11929 - I'll add these to my list of things to get done this week

[everettraven]

@Priyankasaggu11929 I've pushed updates to the repo to address the outstanding items.

Let me know if there is anything else needed from my end.

Thank you!

[Priyankasaggu11929]

I've pushed updates to the repo to address the outstanding items.

Thank you @everettraven. I've invited you to an intermediate GitHub organisation – Kubernetes-purgatory.

Please transfer the crdify repo to above github org. I'll then transfer it further to kubernetes-sigs. Thanks!

[everettraven]

@Priyankasaggu11929 Transfer to kubernetes-purgatory is done, thanks!

[Priyankasaggu11929]

/assign

New repo is created – https://github.com/kubernetes-sigs/crdify

PR to add GitHub teams for the new repo – #5620

@everettraven, the new repo will be a new subproject under SIG API Machinery? or part of an existing subproject?

[everettraven]

New subproject under SIG API Machinery