sig-network iptables-wrappers subproject

[danwinship]

New Repo, Staging Repo, or migrate existing

migrate existing, https://github.com/danwinship/iptables-wrappers

Requested name for new repository

iptables-wrappers

Which Organization should it reside

kubernetes-sigs

If not a staging repo, who should have admin access

danwinship, caseydavenport, dcbw, thockin

If not a staging repo, who should have write access

danwinship, caseydavenport, dcbw, thockin

If not a staging repo, who should be listed as approvers in OWNERS

danwinship

If not a staging repo, who should be listed in SECURITY_CONTACTS

danwinship

What should the repo description be

Wrapper scripts for using iptables in containers

What SIG and subproject does this fall under in sigs.yaml

new subproject for sig-network called iptables-wrappers

Approvals

Originally discussed in January 23, 2020 SIG meeting. Raised on mailing list to no objections. In particular, +1'ed by Tim.

[nikhita]

@danwinship sorry for the delay on this!

Can you update the copyright headers from the Red Hat boilerplate to Kubernetes one? You can find the k8s one here - https://github.com/kubernetes/kubernetes/tree/master/hack/boilerplate.

Looks good to go after that! I have invited you to the https://github.com/kubernetes-purgatory org. Once the boilerplates have been updated, can you move the repo to this dummy org? I can then migrate it to kubernetes-sigs from there.

GitHub doesn't allow adding admins to repos tied to personal accounts (i.e. non-org accounts). This requires us to move the repo to a (dummy) org first.

[nikhita]

/assign

[danwinship]

Fixed the boilerplate and also updated the OWNERS file to add the sig-network team leads as approvers. It is now moved to kubernetes-purgatory.

[nikhita]

Repo has been migrated: https://github.com/kubernetes-sigs/iptables-wrappers 👍

Also created:

• Add GitHub teams for iptables-wrappers #1706 - to create GitHub teams to grant access
• sig-network: add iptables-wrappers subproject community#4597 - to update sigs.yaml

Once both PRs merge, we can close this issue.

[nikhita]

All PRs have merged and teams have been granted access.

/close

[k8s-ci-robot]

@nikhita: Closing this issue.

In response to this:

All PRs have merged and teams have been granted access.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.