Repository navigation
REQUEST: Repository migration github.com/aojea/kindnet #5801
Description
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
Activity
aojea commentedon Aug 29, 2025
/assign @danwinship @BenTheElder @thockin
danwinship commentedon Aug 29, 2025
Last chance to rename... during the meeting yesterday, Shane and Mike both seemed to be assuming that it was kind-specific
thockin commentedon Aug 29, 2025
No objection, but I wish the docs explained the project more :)
Priyankasaggu11929 commentedon Sep 11, 2025
/assign
Confirming - for the scope of this request, are we moving ahead with
kindnetas 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.mdfiles.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 commentedon Sep 11, 2025
Hi
According the EasyCLA status here, i already signed
kubernetes-sigs/contributor-playground#2121
Priyankasaggu11929 commentedon Sep 11, 2025
Thanks for confirming! 👍
aojea commentedon Oct 2, 2025
Ok, I will wait another week otherwise I will follow the rules
sebastianczech commentedon Oct 2, 2025
hi @aojea
according to message
EasyCLA check passed. You are authorized to contribute.from kubernetes-sigs/contributor-playground#2179, I have signed CLA.aojea commentedon Oct 14, 2025
@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.
Priyankasaggu11929 commentedon Oct 14, 2025
Hello @aojea, I think the only thing left before we transfer is the following bit, rest can now happen post transfer
Also, confirming, we are moving ahead with
kindnetas the repo name?aojea commentedon Oct 14, 2025
Done aojea/kindnet#291
yeah, @BenTheElder commented somewhere that is easier this way, because we can always rename later
Priyankasaggu11929 commentedon Oct 14, 2025
@aojea, I've invited you to the intermediary org -
kubernetes-purgatory. Please transfer the repo in that org, I will transfer it further tokubernetes-sigs.aojea commentedon Oct 14, 2025
@Priyankasaggu11929 pushed
Priyankasaggu11929 commentedon Oct 14, 2025
/assign
New repo is created – https://github.com/kubernetes-sigs/kindnet
GitHub teams for the new repo – #5923
k/community documentation - kubernetes/community#8654
Once above PRs are merged, the repo transfer request will be complete.
aojea commentedon Oct 15, 2025
It seems we are all set,
Thanks