REQUEST: Repository migration github.com/aojea/kindnet

[aojea]

New repo, staging repo, or migrate existing

migrate

Is it a staging repo?

no

Requested name for new repository

kindnet

Which Organization should it reside

kubernetes-sigs

Who should have admin access?

aojea, bentheelder, danwinship, thockin

Who should have write access?

aojea, bentheelder, danwinship, thockin

Who should be listed as approvers in OWNERS?

aojea, bentheelder, danwinship, thockin

Who should be listed in SECURITY_CONTACTS?

aojea, bentheelder, danwinship, thockin

What should the repo description be?

minimalistic Kubernetes network plugin that just works

What SIG and subproject does this fall under?

SIG Network

Please provide references to appropriate approval for this new repo

Discussed during SIG Network meeting 28/08/2025, see notes in:

https://docs.google.com/document/d/1_w77-zG_Xj0zYvEMfQZTQ-wPP4kXkpGD8smVtW_qqWM/edit?tab=t.0#

There is some discussion about the naming, but per Ben comments on the docs, it seems that renaming is simple.
I would propose to keep kindnet to simplify the migration process, and rename it after (if there is the desire to do it).

Additional context for request

No response

[aojea]

/assign @danwinship @BenTheElder @thockin

[danwinship]

Requested name for new repository

kindnet

Last chance to rename... during the meeting yesterday, Shane and Mike both seemed to be assuming that it was kind-specific

[thockin]

No objection, but I wish the docs explained the project more :)

[Priyankasaggu11929]

/assign

Requested name for new repository

kindnet

Last chance to rename... during the meeting yesterday, Shane and Mike both seemed to be assuming that it was kind-specific

Confirming - for the scope of this request, are we moving ahead with kindnet as the repo name OR this is still an open item for discussion?

---

@aojea – 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.
  We're missing - CONTRIBUTING.md, RELEASE.md, OWNERS*, SECURITY*, code-of-conduct.md files.

• 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 kindnet repo have signed the CNCF CLA.

  @mhines01 @oshoval @sebastianczech @zx-zx – 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).

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

[oshoval]

Hi
According the EasyCLA status here, i already signed
kubernetes-sigs/contributor-playground#2121

[Priyankasaggu11929]

Hi According the EasyCLA status here, i already signed kubernetes-sigs/contributor-playground#2121

Thanks for confirming! 👍

[aojea]

Ok, I will wait another week otherwise I will follow the rules

If (a) contributor(s) have not signed the CLA and could not be reached, a NOTICE file should be added referencing section 7 of the CLA with a list of the developers who could not be reached

• @mhines01
• @oshoval
• @sebastianczech
• @zx-zx

[sebastianczech]

hi @aojea
according to message EasyCLA check passed. You are authorized to contribute. from kubernetes-sigs/contributor-playground#2179, I have signed CLA.

[aojea]

@Priyankasaggu11929 added NOTICE file to unblock the migration aojea/kindnet@0daccb5

I have the kubernetes templates files in this PR aojea/kindnet#291 and I have modified the licenses headers, but I wonder if we can do that directly on the staging repo to avoid having to merge that in the original repo.