-
Notifications
You must be signed in to change notification settings - Fork 692
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New (staging) repo for k8s network information distributor / aka kube-proxy2 #2410
Comments
@nikhita thanks for your answer, on the "staging" part, it's what looked like my idea, but it's incubating, ie publishing the code in the k8s realm so others can contribute, until we reach the next stage. |
A staging repo, as fart as I understand, exists in k/k/staging/src/k8s.io/... - I do not think that's what we want here. As for names, I am terrible at naming things but I can filter some out :) "knid" is too close to "kind" Throwing some suggestions: epsel - the endpoints selector brainstorm! |
(Drive-by comment to say I like kpng and kpow. 🙃) |
kest - kubernetes endpoints & services transport (pronounced "quest") |
ksept - works too (service endpoints transport), where sept is seven in french, and the number of edges in the k8s logo |
seems like kpng is the winner here so let's go for it ;-) |
I can live with kpng - it's not like we can't change it as we evolve it. |
+1 to |
@mcluseau is the repo meant to contain code migrated from https://github.com/mcluseau/kube-proxy2? If so, can you update the |
@nikhita ok wilco and notify here when done, thanks :) |
ok, I think I've gone through the checklist |
@mcluseau Can you also update the template files to match the repo? For instance, these files would need update - README.md, OWNERS, OWNERS_ALIASES (this can be deleted if not needed), and SECURITY_CONTACTS. |
ohhh... ok... I'm responsible of those too now, that's something real 😱 ;-) |
@mcluseau if you are in the OWNERS file, you also need to be a member of the @kubernetes-sigs GitHub organization to be able to approve PRs. Can you create an issue to request membership? Detailed instructions are here - https://github.com/kubernetes/community/blob/master/community-membership.md#member |
/milestone v1.21 |
@mcluseau I think we're good to go ahead with the migration! Can you move https://github.com/mcluseau/kube-proxy2 to https://github.com/kubernetes-purgatory? (you should have an invite) I'll need admin access to the repo to be able to migrate it to k-sigs, but GitHub doesn't allow adding admins to user-owned repos so we'll need to migrate it to a dummy org first. |
Hi @nikhita , yes the time has come :) I pushed under the voted name (kpng): https://github.com/kubernetes-purgatory/kpng |
Repo has been migrated - https://github.com/kubernetes-sigs/kpng Also created:
Once both PRs merge, this issue can be closed. |
All PRs have merged and teams have been granted access. Closing. |
New Repo, Staging Repo, or migrate existing
new repository (can migrate from https://github.com/mcluseau/kube-proxy2)
Requested name for new repository
Edit (nikhita): final name is
kpng
. See discussion below.TBD: the name is not yet decided. Proposals:
Which Organization should it reside
kubernetes-sigs / sig-network
If not a staging repo, who should have admin access
staging repo
If not a staging repo, who should have write access
staging repo
If not a staging repo, who should be listed as approvers in OWNERS
staging repo
If not a staging repo, who should be listed in SECURITY_CONTACTS
staging repo
What should the repo description be
depends on the chosen name
What SIG and subproject does this fall under in sigs.yaml
this is a new subproject for sig-network called [TBD: chosen name]
Approvals
Creation advised by @thockin
The text was updated successfully, but these errors were encountered: